commit | a97ac2051cedfd32a37a5a7f802a90cd4028079e | [log] [tgz] |
---|---|---|
author | David Drysdale <[email protected]> | Thu Oct 05 10:39:37 2023 +0000 |
committer | Automerger Merge Worker <[email protected]> | Thu Oct 05 10:39:37 2023 +0000 |
tree | 6aa8528344c6a6ed502b8f054341a31baa8ad140 | |
parent | 7f6a5bff23f034b6bad5cc1324d3cd82c95546db [diff] | |
parent | 4e3d0b90442a64ce968343000fd402c7b5d05542 [diff] |
Add baremetal _nostd variant am: 3ce2d52364 am: 51f88e96b2 am: 85357912ff am: 4e3d0b9044 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2769783 Change-Id: Ie47513e9b4942e2b81c6433dc47a8dc0c20ae679 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.