| commit | 17facfa2df4cb22693b9524756bfcd09e30bc5e9 | [log] [tgz] |
|---|---|---|
| author | Sam Saccone <samccone@google.com> | Tue Jul 18 20:00:10 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jul 18 20:00:10 2023 +0000 |
| tree | b4edd6959bec305bc60ba14af775f296410419e5 | |
| parent | 8bc3ea885289d2661b58c00e71fd33a381e55d57 [diff] | |
| parent | 54e63c67844ca9d142d75fded0bc57766e01f695 [diff] |
Move OWNER reference master=>main. am: 54e63c6784 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2662751 Change-Id: Icfa11d48570dc1b6d42c4e3976642e882fdb0205 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.