Struct sequoia_openpgp::packet::signature::subpacket::Subpacket [−][src]
pub struct Subpacket { /* fields omitted */ }Expand description
Signature subpackets.
Most of a signature’s attributes are not stored in fixed fields,
but in so-called subpackets. These subpackets are stored in a
Signature’s so-called subpacket areas, which are effectively
small key-value stores. The keys are subpacket tags
(SubpacketTag). The values are well-structured
(SubpacketValue).
In addition to their key and value, subpackets also include a critical flag. When set, this flag indicates to the OpenPGP implementation that if it doesn’t understand the subpacket, it must consider the signature to be invalid. (Likewise, if it isn’t set, then it means that it is safe for the implementation to ignore the subpacket.) This enables forward compatibility with security-relevant extensions.
It is possible to control how Sequoia’s higher-level functionality
handles unknown, critical subpackets using a Policy object.
Depending on the degree of control required, it may be sufficient
to customize a StandardPolicy object using, for instance, the
StandardPolicy::accept_critical_subpacket method.
The subpacket system is extensible in two ways. First, although
limited, the subpacket name space is not exhausted. So, it is
possible to introduce new packets. Second, one of the subpackets,
the Notation Data subpacket (NotationData), is explicitly
designed for adding arbitrary data to signatures.
Subpackets are described in Section 5.2.3.1 of RFC 4880.
Implementations
Returns the Subpacket’s tag.
Returns the Subpacket’s value.
Returns whether the information in this subpacket has been authenticated.
There are three ways a subpacket can be authenticated:
- It is in the hashed subpacket area and the signature has been verified.
- It is in the unhashed subpacket area and the information is self-authenticating and has been authenticated by Sequoia. This is can be done for issuer information and embedded Signatures.
- The subpacket has been authenticated by the user and
marked as such using
Subpacket::set_authenticated.
Note: The authentication is only valid in the context of the
signature the subpacket is in. If the Subpacket is cloned,
or a Subpacket is added to a SubpacketArea, the flag is
cleared.
Marks the information in this subpacket as authenticated or not.
See Subpacket::authenticated for more information.
Trait Implementations
This method returns an ordering between self and other values if one exists. Read more
This method tests less than (for self and other) and is used by the < operator. Read more
This method tests less than or equal to (for self and other) and is used by the <=
operator. Read more
This method tests greater than (for self and other) and is used by the > operator. Read more
Auto Trait Implementations
impl RefUnwindSafe for Subpacket
impl UnwindSafe for Subpacket
Blanket Implementations
Mutably borrows from an owned value. Read more