| commit | 2c00683ee756c0a4cfe8bf7382d2d19e406fe6e8 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Fri Nov 10 06:54:57 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri Nov 10 06:54:57 2023 +0000 |
| tree | 8d965c3447cfa53c2963fc75caf4007ba05372c5 | |
| parent | abe52fc52a1ee45eb340d7bd76692a2d219bd665 [diff] | |
| parent | 1964b2c594924c3d14b50465f647f4e7ef9dc6fe [diff] |
Use dep-suffixes rather than dependency_suffix. am: 06448c9225 am: 65f87da555 am: 1964b2c594 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2822525 Change-Id: Iac01cedcaaa376b46620e8d21cc60ad54d083b49 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.