Long-Term Supported Versions

    Installing secGear


    openEuler 21.03, openEuler 20.03 LTS SP2, or later

    CPU Architecture


    The Intel Software Guard Extensions (Intel SGX) function is required.


    • Hardware

      ServerTaiShan 200 server (model 2280, dual sockets)
      MainboardKunpeng board
      BMC1711 board (model BC82SMMAB)
      CPUKunpeng 920 processor (model 7260, 5250, or 5220)
      ChassisNo special requirements; an 8- or 12-drive chassis recommended

      The TrustZone feature, including the iTrustee secure OS, BMC firmware, and BIOS firmware, has been installed on the server.

    • Environment Requirements

      The patch in the rich execution environment (REE) is required by a client application (CA) to communicate with a trusted application (TA) in the trusted execution environment (TEE). Before installing secGear, set up the environment as follows:

      1. Setting Up the TA and CA Operating Environment

      2. Applying for a TA Developer Certificate in a Debugging Environment

    Installation Guide

    To use the secGear confidential computing programming framework, you need to install the secGear and secGear-devel development packages. Before the installation, ensure that the openEuler Yum source has been configured.

    1. Install the secGear component with root permissions:

      yum install secGear
      yum install secGear-devel
    2. Run the following commands to check whether the installation is successful. If the command output contains the corresponding software package, the installation is successful.

      rpm -q secGear 
      rpm -q secGear-devel

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    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.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

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


    ● 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
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份