What Cryptography Algorithms Does DEW Use?
Key Algorithms and Specifications Supported by KMS
| Key Type | Algorithm Type | Key Specifications | Description | Scenario |
|---|---|---|---|---|
| Symmetric key | AES | AES_256 (AES-256-GCM authentication encryption) | AES symmetric key |
|
| Digest key | SHA |
| Digest key |
|
| Asymmetric key | RSA |
| RSA asymmetric key |
|
| Asymmetric key | ECC |
| Elliptic curve recommended by NIST | Digital signature and signature verification |
Table 2 describes the encryption and decryption algorithms supported for user-imported keys.
| Algorithm | Description | Configuration |
|---|---|---|
| RSAES_OAEP_SHA_256 | RSA algorithm that uses OAEP and has the SHA-256 hash function | Select an algorithm based on your HSM functions. If the HSMs support the RSAES_OAEP_SHA_256 algorithm, use RSAES_OAEP_SHA_256 to encrypt key materials. NOTICE: The RSAES_OAEP_SHA_1 algorithm is no longer secure. Exercise caution when performing this operation. |
| RSAES_OAEP_SHA_1 | RSA algorithm that uses Optimal Asymmetric Encryption Padding (OAEP) and has the SHA-1 hash function |
Cryptographic Algorithms Supported by KPS
- The SSH key pairs created on the management console support the following cryptographic algorithms:
- SSH-ED25519
- ECDSA-SHA2-NISTP256
- ECDSA-SHA2-NISTP384
- ECDSA-SHA2-NISTP521
- SSH_RSA: The length can be 2,048, 3,072, or 4,096 bits.
- The SSH keys imported to the KPS console support the following cryptographic algorithms:
- SSH-DSS (not recommended)
- SSH-ED25519
- ECDSA-SHA2-NISTP256
- ECDSA-SHA2-NISTP384
- ECDSA-SHA2-NISTP521
- SSH_RSA: The length can be 2,048, 3,072, or 4,096 bits.
Supported Cryptography Algorithms
You can use international common cryptographic algorithms to meet various user requirements.
| Category | Common Cryptographic Algorithm |
|---|---|
| Symmetric cryptographic algorithm | AES |
| Asymmetric cryptographic algorithm | RSA, DSA, ECDSA, DH, and ECDH |
| Digest algorithm | SHA1, SHA256, and SHA384 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.