| commit | 9b342833239cb808c26a3d74b8fc2e9d9c8105ea | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Tue Dec 19 11:09:05 2023 +0000 |
| committer | Gerrit Code Review <[email protected]> | Tue Dec 19 11:09:09 2023 +0000 |
| tree | 01c86a3a6566ea4773d74003c7510a2346d5f5c3 | |
| parent | 2fce4bf4c186d879b631739a1440b708cac7091f [diff] |
Revert^2 "Upgrade const-oid to 0.9.6" 2fce4bf4c186d879b631739a1440b708cac7091f Change-Id: I8444af899cf1765ca5f939cbb4e45762e78126c2
Const-friendly implementation of the ISO/IEC Object Identifier (OID) standard as defined in ITU X.660, with support for BER/DER encoding/decoding as well as heapless no_std (i.e. embedded) environments.
Object Identifiers, a.k.a. OIDs, are an International Telecommunications Union (ITU) and ISO/IEC standard for naming any object, concept, or “thing” with a globally unambiguous persistent name.
The ITU‘s X.660 standard provides the OID specification. Every OID is part of a hierarchical namespace which begins with a root OID, which is either the ITU’s root OID (0), the ISO's root OID (1), or the joint ISO/ITU root OID (2).
The following is an example of an OID, in this case identifying the rsaEncryption algorithm:
1.2.840.113549.1.1.1
For more information, see: https://en.wikipedia.org/wiki/Object_identifier
This library supports parsing OIDs in const contexts, e.g.:
use const_oid::ObjectIdentifier; pub const MY_OID: ObjectIdentifier = ObjectIdentifier::new_unwrap("1.2.840.113549.1.1.1");
The OID parser is implemented entirely in terms of const fn and without the use of proc macros.
Additionally, it also includes a const fn OID serializer, and stores the OIDs parsed from const contexts encoded using the BER/DER serialization (sans header).
This allows ObjectIdentifier to impl AsRef<[u8]> which can be used to obtain the BER/DER serialization of an OID, even one declared const.
Additionally, it impls FromStr and TryFrom<&[u8]> and functions just as well as a runtime OID library.
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.