mirror of
https://gitee.com/openharmony/security_huks
synced 2025-03-04 16:37:19 +00:00
commit
d934955f4c
14
README.md
14
README.md
@ -6,22 +6,24 @@
|
||||
|
||||
## Introduction<a name="section11660541593"></a>
|
||||
|
||||
Harmony Universal KeyStore \(HUKS\) provides key library capabilities for applications, such as key management and cryptographic operations on keys. HUKS also provides APIs for applications to import or generate keys.
|
||||
Harmony Universal KeyStore \(HUKS\) provides applications with key library capabilities, such as key management and cryptographic operations on keys. HUKS also provides APIs for applications to import or generate keys.
|
||||
|
||||
HUKS consists of the following modules:
|
||||
|
||||
- HUKS SDK layer: provides HUKS APIs for applications.
|
||||
|
||||
- HUKS service layer: implements functions such as HUKS key management and storage.
|
||||
- HUKS engine layer: HUKS core module, which generates, encrypts, and decrypts keys. In a commercial version for L2 devices, this module must run in a secure environment such as a TEE or a chip with security capabilities. A secure environment requires dedicated hardware and is therefore implemented only by emulation in the open-source code.
|
||||
- HUKS engine layer: HUKS core module, which generates, encrypts, and decrypts keys. For devices running a standard system, this module of the commercial version must run in a secure environment such as a TEE or a chip with security capabilities. A secure environment requires dedicated hardware and is therefore implemented only by emulation in the open-source code. For the small and mini systems, HUKS only provides the example implementation of the root key protection solution. In commercial scenarios, the implementation must adapt to hardware root key or other root key protection solutions.
|
||||
|
||||
## Directory Structure<a name="section161941989596"></a>
|
||||
|
||||
```
|
||||
base/security/huks/
|
||||
├── build # Build configuration file
|
||||
├── frameworks # Framework code, which is used by interfaces and services
|
||||
│ └── huks_standard # HUKS module in a standard system
|
||||
| └── huks_lite # L0 and L1 code implementation
|
||||
│ └── huks_standard # HUKS implementation
|
||||
| └── huks_lite # HUKS build script in a mini or small system
|
||||
| └── crypto_lite # Encryption and decryption implementation
|
||||
├── interfaces # APIs
|
||||
│ └── innerkits
|
||||
│ └── huks_standard
|
||||
@ -32,4 +34,6 @@ base/security/huks/
|
||||
|
||||
## Repositories Involved<a name="section1371113476307"></a>
|
||||
|
||||
**base/security/huks**
|
||||
**Security subsystem**
|
||||
|
||||
**security_huks**
|
@ -13,7 +13,7 @@ HUKS模块可以分为如下三大部分:
|
||||
- HUKS SDK层:提供HUKS API供应用调用。
|
||||
|
||||
- HUKS Service层:实现HUKS密钥管理、存储等功能。
|
||||
- HUKS Engine层:HUKS核心模块,负责密钥生成以及加解密等工作。对于L2设备,该部分模块在商用场景下必须在安全环境下运行,包括TEE或者具备安全能力的芯片等。由于安全环境需要特定硬件支持,因此在开源代码中为模拟实现。
|
||||
- HUKS Engine层:HUKS核心模块,负责密钥生成以及加解密等工作。对于标准系统设备,该部分模块在商用场景下必须在安全环境下运行,包括TEE或者具备安全能力的芯片等。由于安全环境需要特定硬件支持,因此在开源代码中为模拟实现。对于小型和轻量系统,HUKS模块仅提供根密钥保护方案的模拟实现,商用场景下必须根据产品能力适配硬件根密钥或者使用其他根密钥保护方案。
|
||||
|
||||
## 目录<a name="section161941989596"></a>
|
||||
|
||||
@ -21,8 +21,8 @@ HUKS模块可以分为如下三大部分:
|
||||
base/security/huks/
|
||||
├── build # 编译配置文件
|
||||
├── frameworks # 框架代码, 作为基础功能目录, 被interfaces和services使用.
|
||||
│ └── huks_standard # huks标准模块, 即表示L2的HUKS模块
|
||||
│ └── huks_lite # huks L0和L1代码实现
|
||||
│ └── huks_standard # 代码实现
|
||||
│ └── huks_lite # 小型和轻量系统编译脚本
|
||||
│ └── crypto_lite # 加解密实现
|
||||
├── interfaces # 接口API代码
|
||||
│ └── innerkits
|
||||
|
Loading…
x
Reference in New Issue
Block a user