commit | 88b2a4033dd47e2b79321d6c92a59d2c613f59ad | [log] [tgz] |
---|---|---|
author | Xin Li <[email protected]> | Mon Apr 29 11:50:42 2024 -0700 |
committer | Xin Li <[email protected]> | Mon Apr 29 11:50:42 2024 -0700 |
tree | 5a7065bc5b4a5a32656d90ef4ae8c6549ae9c029 | |
parent | 101772614598511da6ad4a4bf53c07a0881dcf75 [diff] | |
parent | 747c687311d336b35829e428fb07a48df6efc38f [diff] |
Empty merge of Android 24Q2 Release (ab/11526283) to aosp-main-future Bug: 337098550 Merged-In: Idd2570035e39475f035a00921ae7d5b46fb78f90 Change-Id: I9c7b4a8239c33719398d4cbdd6501b0eff888044
Pure Rust implementation of Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification (RFC 5208).
PKCS#8 is a format for cryptographic private keys, often containing pairs of private and public keys.
You can identify a PKCS#8 private key encoded as PEM (i.e. text) by the following:
-----BEGIN PRIVATE KEY-----
PKCS#8 private keys can optionally be encrypted under a password using key derivation algorithms like PBKDF2 and scrypt, and encrypted with ciphers like AES-CBC. When a PKCS#8 private key has been encrypted, it starts with the following:
-----BEGIN ENCRYPTED PRIVATE KEY-----
PKCS#8 private keys can also be serialized in an ASN.1-based binary format. The PEM text encoding is a Base64 representation of this format.
This crate is implemented in an algorithm-agnostic manner with the goal of enabling PKCS#8 support for any algorithm.
That said, it has been tested for interoperability against keys generated by OpenSSL for the following algorithms:
id-ecPublicKey
)id-Ed25519
)id-rsaEncryption
)id-X25519
)Please open an issue if you encounter trouble using it with a particular algorithm, including the ones listed above or other algorithms.
This crate requires Rust 1.65 at a minimum.
We may change the MSRV in the future, but it will be accompanied by a minor version bump.
Licensed under either of:
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.