commit | 8bc3ea885289d2661b58c00e71fd33a381e55d57 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <[email protected]> | Thu Mar 09 17:04:39 2023 +0000 |
committer | Automerger Merge Worker <[email protected]> | Thu Mar 09 17:04:39 2023 +0000 |
tree | 01494fbe8402a4986a4ac4e249136f1d092d9467 | |
parent | a551d45abcc9afd314960537b936ced5df480429 [diff] | |
parent | 9ceaaef5fa5a811fc4524ec98d0658a999fec5c9 [diff] |
Make pkcs8 available to product and vendor am: 64a7cd221f am: bc10e19e3d am: 9ceaaef5fa Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2476391 Change-Id: I21a058d26ca3db7a951921b20300a6ac145b79e0 Signed-off-by: Automerger Merge Worker <[email protected]>
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.57 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.