commit | abe52fc52a1ee45eb340d7bd76692a2d219bd665 | [log] [tgz] |
---|---|---|
author | Per Larsen <perlarsen@google.com> | Thu Nov 09 02:05:58 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 09 02:05:58 2023 +0000 |
tree | 84590a8a60a9f6f5bb036341cdf4621c9eb08d26 | |
parent | 46551087f3a7175e18adc13b1afb0df6e033a358 [diff] | |
parent | b628f24098b597b0584f51db971f7b8580c1540b [diff] |
Adding autogenerated Trusty makefile rules am: 6641344525 am: f4049f70c3 am: b628f24098 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pkcs8/+/2753365 Change-Id: I9623f1faa89fea0b00cd13364ff43c144469f919 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.