X.509 parser written in pure Rust. Fast, zero-copy, safe.
  • Rust 99.6%
  • Python 0.4%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-04-07 18:06:09 +02:00
assets Add value field to ParsedExtension::UnsupportedExtension 2025-05-27 08:27:40 +00:00
examples fix(verify): also enable all functions when using verify-aws 2025-09-01 08:53:21 +00:00
fuzz chore: sync dependencies (monorepo) 2026-03-30 14:57:03 +02:00
src chore: sync dependencies (monorepo) 2026-04-07 18:06:09 +02:00
tests chore: sync dependencies (monorepo) 2026-03-30 14:57:03 +02:00
.gitignore Add value field to ParsedExtension::UnsupportedExtension 2025-05-27 08:27:40 +00:00
Cargo.lock Run cargo update 2025-09-01 08:11:16 +00:00
Cargo.toml chore: sync dependencies (monorepo) 2026-04-06 21:15:05 +02:00
LICENSE-APACHE Switch license to MIT + APLv2 2018-01-17 08:19:03 +01:00
LICENSE-MIT Switch license to MIT + APLv2 2018-01-17 08:19:03 +01:00
README.md fix(verify): also enable all functions when using verify-aws 2025-09-01 08:53:21 +00:00

License: MIT Apache License 2.0 docs.rs crates.io Download numbers Github CI Minimum rustc version

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 X509Certificate::from_der ( part of the FromDer trait ), which builds a X509Certificate object.

An alternative method is to use X509CertificateParser, which allows specifying parsing options (for example, not automatically parsing option contents).

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.

This crate also provides visitor traits: X509CertificateVisitor.

Examples

Parsing a certificate in DER format:

use x509_parser::prelude::*;

static IGCA_DER: &[u8] = include_bytes!("../assets/IGC_A.der");

let res = X509Certificate::from_der(IGCA_DER);
match res {
    Ok((rem, cert)) => {
        assert!(rem.is_empty());
        //
        assert_eq!(cert.version(), X509Version::V3);
    },
    _ => panic!("x509 parsing failed: {:?}", res),
}

To parse a CRL and print information about revoked certificates:

#
#
let res = CertificateRevocationList::from_der(DER);
match res {
    Ok((_rem, crl)) => {
        for revoked in crl.iter_revoked_certificates() {
            println!("Revoked certificate serial: {}", revoked.raw_serial_as_string());
            println!("  Reason: {}", revoked.reason_code().unwrap_or_default().1);
        }
    },
    _ => panic!("CRL parsing failed: {:?}", res),
}

See also examples/print-cert.rs.

Features

  • The verify and verify-aws features adds support for (cryptographic) signature verification, based on ring or aws-lc respectively. It adds the X509Certificate::verify_signature() to X509Certificate.
/// Cryptographic signature verification: returns true if certificate was signed by issuer
#[cfg(any(feature = "verify", feature = "verify-aws"))]
pub fn check_signature(cert: &X509Certificate<'_>, issuer: &X509Certificate<'_>) -> bool {
    let issuer_public_key = issuer.public_key();
    cert
        .verify_signature(Some(issuer_public_key))
        .is_ok()
}
  • The validate features add methods to run more validation functions on the certificate structure and values using the Validate trait. It does not validate any cryptographic parameter (see verify above).

Rust version requirements

x509-parser requires Rustc version 1.67.1 or greater, based on der-parser dependencies and for proc-macro attributes support.

Changes

See CHANGELOG.md and UPGRADING.md for instructions for upgrading major versions.

License

Licensed under either of

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.