1# Crypto Framework Changelog
2
3## cl.crypto_architecture.1 Change of Sign.update and Verify.update
4
5**Access Level**
6
7Public
8
9**Reason for Change**
10
11When DSA algorithm is used for signing or signature verification with the digest algorithm set to **NoHash**, **update()** is not supported. However, **update()** returns a success message.
12
13**Change Impact**
14
15This change is a non-compatible change.
16
17Before the change:<br>When DSA is used for signing with the digest algorithm set to **NoHash**, calling **update()** returns a success message, but the signature generated is incorrect.
18
19After the change:<br>When DSA is used for signing with the digest algorithm set to **NoHash**, calling **update()** returns ERR_CRYPTO_OPERATION.
20
21Before the change:<br>When DSA is used to verify the signature data with the digest algorithm set to **NoHash**, calling **update()** returns a success message, but the signature verification fails.
22
23After the change:<br>When DSA is used to verify the signature data with the digest algorithm set to **NoHash**, calling **update()** returns ERR_CRYPTO_OPERATION.
24
25**Start API Level**
26
2710
28
29**Change Since**
30
31OpenHarmony SDK 5.0.0.22
32
33**Key API/Component Changes**
34
35**Sign.update** and **Verify.update** in @ohos.security.cryptoFramework.d.ts
36
37**Adaptation Guide**
38
39When DSA is used for signing or signature verification and the digest algorithm is set to **NoHash**, do not use **update()**. If **Sign.init** and **Sign.sign** are called in signing, use **Verify.init** and **Verify.verify** or the sync APIs in signature verification.
40