From afca5eecc9ae08917a1389bc06a2ee372b556935 Mon Sep 17 00:00:00 2001 From: Annie_wang Date: Thu, 27 Oct 2022 16:21:32 +0800 Subject: [PATCH] update docs Signed-off-by: Annie_wang --- en/application-dev/security/huks-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/application-dev/security/huks-overview.md b/en/application-dev/security/huks-overview.md index bf7de59ac4..2fd486ae76 100644 --- a/en/application-dev/security/huks-overview.md +++ b/en/application-dev/security/huks-overview.md @@ -12,7 +12,7 @@ Openharmony Universal KeyStore (HUKS) provides KeyStore (KS) capabilities for ap ### Working Principles -HUKS manages keys through the following operations: +HUKS manages keys through the following APIs in an Init-Update-Finish model: - **Init**: reads the key, creates a session ID, and returns the session ID to the caller. @@ -20,7 +20,7 @@ HUKS manages keys through the following operations: - **Finish**: processes all data transferred to HUKS and then releases resources. - >![](../public_sys-resources/icon-notice.gif)**NOTICE**:
If an error occurs in the **Init**, **Update**, or **Finish** operation, you must invoke the **Abort** operation to terminate the use of the key. + >![](../public_sys-resources/icon-notice.gif)**NOTICE**:
**Abort()** must be called to terminate the use of the key when an error occurs in any of **Init()**, **Update()**, and **Finish()**. ### Constraints -- GitLab