X.509 Parser
A X.509 v3 (RFC5280) parser, implemented with the nom parser combinator framework.
It is written in pure Rust, fast, and makes extensive use of zero-copy. A lot of care is taken to ensure security and safety of this crate, including design (recursion limit, defensive programming), tests, and fuzzing. It also aims to be panic-free.
The code is available on Github and is part of the Rusticata project.
Certificates are usually encoded in two main formats: PEM (usually the most common format) or
DER. A PEM-encoded certificate is a container, storing a DER object. See the
pem
module for more documentation.
To decode a DER-encoded certificate, the main parsing method is
parse_x509_certificate
, which builds a
X509Certificate
object.
The returned objects for parsers follow the definitions of the RFC. This means that accessing
fields is done by accessing struct members recursively. Some helper functions are provided, for
example X509Certificate::issuer() returns the
same as accessing <object>.tbs_certificate.issuer
.
For PEM-encoded certificates, use the pem
module.
Examples
Parsing a certificate in DER format:
use *;
static IGCA_DER: & = include_bytes!;
let res = parse_x509_certificate;
match res
To parse a CRL and print information about revoked certificates:
#
#
let res = parse_x509_crl;
match res
See also examples/print-cert.rs
.
Features
- The
verify
feature adds support for (cryptographic) signature verification, based onring
. It adds the X509Certificate::verify_signature() toX509Certificate
.
/// Cryptographic signature verification: returns true if certificate was signed by issuer
Rust version requirements
x509-parser
requires Rustc version 1.45 or greater, based on nom 6
dependencies and for proc-macro attributes support.
Changes
See CHANGELOG.md
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
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.