Enum CertUsage

pub enum CertUsage {
    PkixTa,
    PkixEe,
    DaneTa,
    DaneEe,
    Unassigned(u8),
    Private,
}

RFC 6698, DNS-Based Authentication for TLS

2.1.1.  The Certificate Usage Field

   A one-octet value, called "certificate usage", specifies the provided
   association that will be used to match the certificate presented in
   the TLS handshake.  This value is defined in a new IANA registry (see
   Section 7.2) in order to make it easier to add additional certificate
   usages in the future.  The certificate usages defined in this
   document are:

      0 -- CA

      1 -- Service

      2 -- TrustAnchor

      3 -- DomainIssued

   The certificate usages defined in this document explicitly only apply
   to PKIX-formatted certificates in DER encoding [X.690].  If TLS
   allows other formats later, or if extensions to this RRtype are made
   that accept other formats for certificates, those certificates will
   need their own certificate usage values.

RFC 7218, Adding Acronyms to DANE Registries

2.1.  TLSA Certificate Usages Registry

  The reference for this registry has been updated to include both
  [RFC6698] and this document.

   +-------+----------+--------------------------------+-------------+
   | Value | Acronym  | Short Description              | Reference   |
   +-------+----------+--------------------------------+-------------+
   |   0   | PKIX-TA  | CA constraint                  | [RFC6698]   |
   |   1   | PKIX-EE  | Service certificate constraint | [RFC6698]   |
   |   2   | DANE-TA  | Trust anchor assertion         | [RFC6698]   |
   |   3   | DANE-EE  | Domain-issued certificate      | [RFC6698]   |
   | 4-254 |          | Unassigned                     |             |
   |  255  | PrivCert | Reserved for Private Use       | [RFC6698]   |
   +-------+----------+--------------------------------+-------------+

Variants

PkixTa

      0 -- Certificate usage 0 is used to specify a CA certificate, or
      the public key of such a certificate, that MUST be found in any of
      the PKIX certification paths for the end entity certificate given
      by the server in TLS.  This certificate usage is sometimes
      referred to as "CA constraint" because it limits which CA can be
      used to issue certificates for a given service on a host.  The
      presented certificate MUST pass PKIX certification path
      validation, and a CA certificate that matches the TLSA record MUST
      be included as part of a valid certification path.  Because this
      certificate usage allows both trust anchors and CA certificates,
      the certificate might or might not have the basicConstraints
      extension present.

PkixEe

      1 -- Certificate usage 1 is used to specify an end entity
      certificate, or the public key of such a certificate, that MUST be
      matched with the end entity certificate given by the server in
      TLS.  This certificate usage is sometimes referred to as "service
      certificate constraint" because it limits which end entity
      certificate can be used by a given service on a host.  The target
      certificate MUST pass PKIX certification path validation and MUST
      match the TLSA record.

DaneTa

      2 -- Certificate usage 2 is used to specify a certificate, or the
      public key of such a certificate, that MUST be used as the trust
      anchor when validating the end entity certificate given by the
      server in TLS.  This certificate usage is sometimes referred to as
      "trust anchor assertion" and allows a domain name administrator to
      specify a new trust anchor -- for example, if the domain issues
      its own certificates under its own CA that is not expected to be
      in the end users' collection of trust anchors.  The target
      certificate MUST pass PKIX certification path validation, with any
      certificate matching the TLSA record considered to be a trust
      anchor for this certification path validation.

DaneEe

      3 -- Certificate usage 3 is used to specify a certificate, or the
      public key of such a certificate, that MUST match the end entity
      certificate given by the server in TLS.  This certificate usage is
      sometimes referred to as "domain-issued certificate" because it
      allows for a domain name administrator to issue certificates for a
      domain without involving a third-party CA.  The target certificate
      MUST match the TLSA record.  The difference between certificate
      usage 1 and certificate usage 3 is that certificate usage 1
      requires that the certificate pass PKIX validation, but PKIX
      validation is not tested for certificate usage 3.

Unassigned(u8)

Unassigned at the time of this implementation

Private

Private usage

Trait Implementations

impl Clone for CertUsage

fn clone(&self) -> CertUsage

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CertUsage

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl From<CertUsage> for u8

fn from(usage: CertUsage) -> u8

Converts to this type from the input type.

impl From<u8> for CertUsage

fn from(usage: u8) -> CertUsage

Converts to this type from the input type.

impl Hash for CertUsage

fn hash<__H>(&self, state: &mut __H)

where __H: Hasher,

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for CertUsage

fn eq(&self, other: &CertUsage) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Copy for CertUsage

impl Eq for CertUsage

impl StructuralPartialEq for CertUsage