Long-Term Supported Versions

    Innovation Versions

      Introduction to Signature Certificates

      openEuler supports two signature mechanisms: openPGP and CMS, which are used for different file types.

      File TypeSignature TypeSignature Format
      EFI filesauthenticodeCMS
      Kernel module filesmodsigCMS
      IMA digest listsmodsigCMS
      RPM software packagesRPMopenPGP

      openPGP Certificate Signing

      openEuler uses openPGP certificates to sign RPM software packages. The signature certificates are released with the OS image. You can obtain certificates used by openEuler in either of the following ways:

      Method 1: Download the certificate from the repository. For example, download the certificate of openEuler 24.03 LTS from the following address:

      https://repo.openeuler.org/openEuler-24.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
      

      Method 2: Log in to the system and obtain the file from the specified path.

      cat /etc/pki/rpm-gpg/RPM-GPG-KEY-openEuler
      

      CMS Certificate Signing

      The openEuler signature platform uses a three-level certificate chain to manage signature private keys and certificates.

      Certificates of different levels have different validity periods. The current plan is as follows:

      TypeValidity Period
      Root certificate30 years
      Level-2 certificate10 years
      Level-3 certificate3 years

      The openEuler root certificate can be downloaded from the community certificate center.

      https://www.openeuler.org/en/security/certificate-center/
      

      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备份