Long-Term Supported Versions

    Innovation Versions

      Installing secGear

      Arm Platform

      Environment Requirements

      Hardware Environment

      ItemSpecification
      ServerTaiShan 200 (model 2280)
      MainboardKunpeng mainboard
      BMC1711 single board (model BC82SMMAB) with firmware version no later than 3.01.12.49
      CPUKunpeng 920 7260, 5250, or 5220
      ChassisNot limited. 8 or 12 drives are recommended.

      imgNote:

      • The server must have built-in TrustZone Kit, that is, TEE OS, TEE OS boot key, BMC, BIOS, and license.
      • TrustZone Kit cannot be enabled on a common server by only upgrading BMC, BIOS, and TEE OS firmware.
      • TrustZone Kit is disabled on the servers by default. Enable TrustZone Kit by referring to the BIOS manual.

      OS

      openEuler 20.03 LTS SP2 or later

      openEuler 22.09

      openEuler 22.03 LTS or later

      Environment Preparation

      For details, see Environment Requirements and Procedure on the Kunpeng community website.

      Installation Procedure

      1. Configure an online or locally mounted openEuler Yum repository. An example online Yum repository configuration is as follows (replace 22.03-LTS with the actual version):

        $ vi openEuler.repo 
        [osrepo]
        name=osrepo
        baseurl=http://repo.openeuler.org/openEuler-22.03-LTS/everything/aarch64/
        enabled=1
        gpgcheck=1
        gpgkey=http://repo.openeuler.org/openEuler-22.03-LTS/everything/aarch64/RPM-GPG-KEY-openEuler
        
      2. Install secGear.

        # Install build tools.
        $ yum install cmake ocaml-dune
        
        # Install secGear.
        $ yum install secGear-devel
        
        # Verify the installation.
        $ rpm -qa | grep -E 'secGear|itrustee|ocaml-dune'
        itrustee_sdk-xxx
        itrustee_sdk-devel-xxx
        secGear-xxx
        secGear-devel-xxx
        ocaml-dune-xxx
        

      x86 Platform

      Environment Requirements

      Hardware Environment

      The processor must support the Intel SGX feature.

      OS

      openEuler 20.03 LTS SP2 or later

      openEuler 22.09

      openEuler 22.03 LTS or later

      Environment Preparation

      Enable the Intel SGX feature by referring to the BIOS manual.

      Installation Procedure

      1. Configure an online or locally mounted openEuler Yum repository. An example online Yum repository configuration is as follows (replace 22.03-LTS with the actual version):

        vi openEuler.repo 
        [osrepo]
        name=osrepo
        baseurl=http://repo.openeuler.org/openEuler-22.03-LTS/everything/x86_64/
        enabled=1
        gpgcheck=1
        gpgkey=http://repo.openeuler.org/openEuler-22.03-LTS/everything/x86_64/RPM-GPG-KEY-openEuler
        
      2. Install secGear.

        # Install build tools.
        $ yum install cmake ocaml-dune
        
        # Install secGear.
        $ yum install secGear-devel
        
        # Verify the installation.
        $ rpm -qa | grep -E 'secGear|ocaml-dune|sgx'
        secGear-xxx
        secGear-devel-xxx
        ocaml-dune-xxx
        libsgx-epid-xxx
        libsgx-enclave-common-xxx
        libsgx-quote-ex-xxx
        libsgx-aesm-launch-plugin-xxx
        libsgx-uae-service-xxx
        libsgx-ae-le-xxx
        libsgx-urts-xxx
        sgxsdk-xxx
        sgx-aesm-service-xxx
        linux-sgx-driver-xxx
        libsgx-launch-xxx
        

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份