| commit | ce65a75d779453543fecebf94796eb4f8033d2a9 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 31 03:05:08 2021 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 31 03:05:08 2021 +0000 |
| tree | 64ec11afda2b7b58dfb4aabebdfab89495080d77 | |
| parent | f298d116ed72573adcad2a255570a6853ee68a31 [diff] | |
| parent | e19a9017ea7d6063cece18ec1b00b565d209a391 [diff] |
Snap for 7688365 from e19a9017ea7d6063cece18ec1b00b565d209a391 to tm-release Change-Id: Iba9ff466b0be1f34a5f629391943b0ea2f0cdbfa
This crate is a helper crate, containing a database of OID objects. These objects are intended for use when manipulating ASN.1 grammars and BER/DER encodings, for example.
This crate provides only a simple registry (similar to a HashMap) by default. This object can be used to get names and descriptions from OID.
This crate provides default lists of known OIDs, that can be selected using the build features. By default, the registry has no feature enabled, to avoid embedding a huge database in crates.
It also declares constants for most of these OIDs.
use oid_registry::OidRegistry; let mut registry = OidRegistry::default() .with_crypto() // only if the 'crypto' feature is enabled ; let e = registry.get(&oid_registry::OID_PKCS1_SHA256WITHRSA); if let Some(entry) = e { // get sn: sha256WithRSAEncryption println!("sn: {}", entry.sn()); // get description: SHA256 with RSA encryption println!("description: {}", entry.description()); }
These provided lists are often incomplete, or may lack some specific OIDs. This is why the registry allows adding new entries after construction:
use oid_registry::{OidEntry, OidRegistry}; use der_parser::oid; let mut registry = OidRegistry::default(); // entries can be added by creating an OidEntry object: let entry = OidEntry::new("shortName", "description"); registry.insert(oid!(1.2.3.4), entry); // when using static strings, a tuple can also be used directly for the entry: registry.insert(oid!(1.2.3.5), ("shortName", "A description"));
All OID values, constants, and features are derived from files in the assets directory in the build script (see build.rs). See load_file for documentation of the file format.
oid-registry requires Rustc version 1.45 or greater, based on proc-macro attributes support.
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.