commit | 28d196edd00ee9c17d6f642617967d8839a29cf8 | [log] [tgz] |
---|---|---|
author | Bob Badour <[email protected]> | Thu Oct 06 23:03:10 2022 +0000 |
committer | Automerger Merge Worker <[email protected]> | Thu Oct 06 23:03:10 2022 +0000 |
tree | 1245908ee9e7d2783654862c7ffb236bc6e64f9d | |
parent | b31164c2b8fcfa0c0cca0c2eedb52ee270e632a2 [diff] | |
parent | 5803e6daad30e3c528474bca825f790aecca0e7a [diff] |
[LSC] Add LOCAL_LICENSE_KINDS to external/rust/crates/pkcs8 am: 06b90b3cd7 am: 5803e6daad Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2242222 Change-Id: Ie90fdf6d0cc29bf1d7ec638275adcd247e4c761e 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.