Long-Term Supported Versions

    Innovation Versions

      secGear Installation

      Arm Environment

      Environment Requirements

      Hardware

      ItemModel
      ServerTaiShan 200 server (model 2280)
      MainboardKunpeng board
      BMC1711 board (model BC82SMMAB); firmware version: 3.01.12.49 or later
      CPUKunpeng 920 processor (model 7260, 5250, or 5220)
      ChassisNo special requirements; an 8- or 12-drive chassis recommended

      imgNOTE

      • Ensure that the TrustZone feature kit has been preconfigured on the server. That is, the TEE OS, TEE OS boot key, BMC, BIOS, and license have been preconfigured on the server.
      • For common servers, the TrustZone feature cannot be enabled only by upgrading the BMC, BIOS, and TEE OS firmware.
      • By default, the TrustZone feature is disabled on the server. For details about how to enable the TrustZone feature on the server, see BIOS settings.

      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 official website.

      Installation

      1. Configure the openEuler Yum source. You can configure an online Yum source or configure a local Yum source by mounting an ISO file. The following uses openEuler 22.03 LTS as an example. For other versions, use the Yum source of the corresponding version.

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

        # Install the compiler.
        yum install cmake ocaml-dune
        
        # Install secGear.
        yum install secGear-devel
        
        # Check whether the installations are successful. If the command output is as follows, the installations are successful.
        $ rpm -qa | grep -E 'secGear|itrustee|ocaml-dune'
        itrustee_sdk-xxx
        itrustee_sdk-devel-xxx
        secGear-xxx
        secGear-devel-xxx
        ocaml-dune-xxx
        

      x86 Environment

      Environment Requirements

      Hardware

      Processor that supports the Intel SGX feature

      OS

      openEuler 20.03 LTS SP2 or later

      openEuler 22.09

      openEuler 22.03 LTS or later

      Environment Preparation

      Purchase a device that supports the Intel SGX feature and enable the SGX feature by referring to the BIOS setting manual of the device.

      Installation

      1. Configure the openEuler Yum source. You can configure an online Yum source or configure a local Yum source by mounting an ISO file. The following uses openEuler 22.03 LTS as an example. For other versions, use the Yum source of the corresponding version.

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

        # Install the compiler.
        yum install cmake ocaml-dune
        
        # Install secGear.
        yum install secGear-devel
        
        # Check whether the installations are successful. If the command output is as follows, the installations are successful.
        $ 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备份