Commit 32a87df
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1019,9 +1019,14 @@ added: v15.0.0 | |||
| 1019 | 1019 | ||
| 1020 | 1020 | * Type: {ArrayBuffer|TypedArray|DataView|Buffer} | |
| 1021 | 1021 | ||
| 1022 | - The initialization vector must be unique for every encryption operation | ||
| 1023 | - using a given key. The AES-GCM specification recommends that | ||
| 1024 | - this contain at least 12 random bytes. | ||
| 1022 | + The initialization vector must be unique for every encryption operation using a | ||
| 1023 | + given key. | ||
| 1024 | + | ||
| 1025 | + Ideally, this is a deterministic 12-byte value that is computed in such a way | ||
| 1026 | + that it is guaranteed to be unique across all invocations that use the same key. | ||
| 1027 | + Alternatively, the initialization vector may consist of at least 12 | ||
| 1028 | + cryptographically random bytes. For more information on constructing | ||
| 1029 | + initialization vectors for AES-GCM, refer to Section 8 of [NIST SP 800-38D][]. | ||
| 1025 | 1030 | ||
| 1026 | 1031 | #### `aesGcmParams.name` | |
| 1027 | 1032 | ||
@@ -1923,5 +1928,6 @@ added: v15.0.0 | |||
| 1923 | 1928 | ||
| 1924 | 1929 | [JSON Web Key]: https://tools.ietf.org/html/rfc7517 | |
| 1925 | 1930 | [Key usages]: #cryptokeyusages | |
| 1931 | + [NIST SP 800-38D]: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf | ||
| 1926 | 1932 | [RFC 4122]: https://www.rfc-editor.org/rfc/rfc4122.txt | |
| 1927 | 1933 | [Web Crypto API]: https://www.w3.org/TR/WebCryptoAPI/ | |
0 commit comments