• Home
Name Date Size #Lines LOC

..--

build/12-May-2024-4937

frameworks/12-May-2024-26,39620,682

interfaces/12-May-2024-13,7988,699

services/huks_standard/12-May-2024-22,83217,294

test/12-May-2024-122,93393,031

utils/12-May-2024-3,0542,362

.gitattributesD12-May-2024631 1615

BUILD.gnD12-May-20242.3 KiB8375

LICENSED12-May-202410.1 KiB177150

README.mdD12-May-20242.1 KiB4433

README_zh.mdD12-May-20242 KiB4733

bundle.jsonD12-May-20242.3 KiB8584

hisysevent.yamlD12-May-2024987 249

huks.gniD12-May-2024847 2522

README.md

1# HUKS<a name="EN-US_TOPIC_0000001148528849"></a>
2
3-   [Introduction](#section11660541593)
4-   [Directory Structure](#section161941989596)
5-   [Repositories Involved](#section1371113476307)
6
7## Introduction<a name="section11660541593"></a>
8
9OpenHarmony 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.
10
11HUKS consists of the following modules:
12
13-   HUKS SDK layer: provides HUKS APIs for applications.
14
15-   HUKS service layer: implements functions such as HUKS key management and storage.
16-   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 the protection solution for either the hardware root key or other root keys.
17
18## Directory Structure<a name="section161941989596"></a>
19
20```
21base/security/huks/
22├── build                            # Build configuration file
23├── frameworks                       # Framework code, which is used by interfaces and services
24│   └── huks_standard                # Code implementation
25|   └── huks_lite                    # Build script in a small and mini systems
26|   └── crypto_lite                  # Encryption and decryption implementation
27├── interfaces                       # APIs
28│   └── innerkits
29│   └── kits
30├── services
31│   └── huks_standard
32├── test
33└── utils
34   └── crypto_adapter
35   └── file_operator
36   └── list
37   └── mutex
38```
39
40## Repositories Involved<a name="section1371113476307"></a>
41
42**Security subsystem**
43
44**[security_huks](https://gitee.com/openharmony/security_huks)**

README_zh.md

1# HUKS组件<a name="ZH-CN_TOPIC_0000001148528849"></a>
2
3-   [简介](#section11660541593)
4-   [目录](#section161941989596)
5-   [相关仓](#section1371113476307)
6
7## 简介<a name="section11660541593"></a>
8
9HUKS(OpenHarmony Universal KeyStore,OpenHarmony通用密钥库系统)向应用提供密钥库能力,包括密钥管理及密钥的密码学操作等功能。HUKS所管理的密钥可以由应用导入或者由应用调用HUKS接口生成。
10
11HUKS模块可以分为如下三大部分:
12
13-   HUKS SDK层:提供HUKS API供应用调用。
14
15-   HUKS Service层:实现HUKS密钥管理、存储等功能。
16-   HUKS Engine层:HUKS核心模块,负责密钥生成以及加解密等工作。对于标准系统设备,该部分模块在商用场景下必须在安全环境下运行,包括TEE或者具备安全能力的芯片等。由于安全环境需要特定硬件支持,因此在开源代码中为模拟实现。对于小型和轻量系统,HUKS模块仅提供根密钥保护方案的模拟实现,商用场景下必须根据产品能力适配硬件根密钥或者使用其他根密钥保护方案。
17
18## 目录<a name="section161941989596"></a>
19
20```
21base/security/huks/
22├── build                             # 编译配置文件
23├── frameworks                        # 框架代码, 作为基础功能目录, 被interfaces和services使用.
24│   └── huks_standard                 # 代码实现
25│   └── huks_lite                     # 小型和轻量系统编译脚本
26│   └── crypto_lite                   # 加解密实现
27├── interfaces                        # 接口API代码
28│   └── innerkits
29│   └── kits
30├── services
31│   └── huks_standard
32├── test
33└── utils
34   └── crypto_adapter
35   └── file_operator
36   └── list
37   └── mutex
38```
39
40## 相关仓<a name="section1371113476307"></a>
41
42**安全子系统**
43
44**[security_huks](https://gitee.com/openharmony/security_huks)**
45
46
47