Enum VerificationStrategy 

pub enum VerificationStrategy {
    CreativeIntegrity,
    AuthoritativeIntegrity,
    GreedyVerification,
    ExhaustiveVerification,
    MultipleAttestation(Vec<SignatureRole>),
    MultipleAttestationGreedy(Vec<SignatureRole>),
}

This enumerates the verifications strategies described in the signing spec.

Variants

CreativeIntegrity

CreativeIntegrity verifies that (a) the key that signs as Creator is a known key, and that the signature is valid.

AuthoritativeIntegrity

AuthoritativeIntegrity verifies that at least one of the Creator or Approver keys is known and the signature is valid.

GreedyVerification

Verify that the Creator key is known and that all signatures are valid.

This is subject to a DOS attack if a signer can generate intentionally bad signatures.

ExhaustiveVerification

Verify that every key on the invoice is known, and that every signature is valid.

MultipleAttestation(Vec<SignatureRole>)

Verifies that all signatures of the given roles are valid and signed by known keys.

MultipleAttestationGreedy(Vec<SignatureRole>)

Verifies that all signatures of the given roles are valid and signed by known keys. Will also validate unknown signers similar to GreedyVerification

Unknown signers will also be validated. Be aware that doing so may make the validation subject to a special form of DOS attack in which someone can generate a known-bad signature.

Implementations

impl VerificationStrategy

A strategy for verifying an invoice.

pub fn verify<I>( &self, invoice: I, keyring: &KeyRing, ) -> Result<VerifiedInvoice<I>, SignatureError>

where I: Borrow<Invoice> + Into<Invoice>,

Verify that every signature on this invoice is correct.

The verification strategy will determine how this verification is performed. Depending on the selected strategy, the [[signature]] blocks will be evaluated for the following:

• Is the key in the keyring?
• Can the signature be verified?

Note that the purpose of the keyring is to ensure that we know about the entity that claims to have signed the invoice.

If no signatures are on the invoice, this will succeed.

A strategy will determine success or failure based on whether the signature is verified, whether the keys are known, whether the requisite number/roles are satisfied, and so on.

Trait Implementations

impl Clone for VerificationStrategy

fn clone(&self) -> VerificationStrategy

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for VerificationStrategy

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

Formats the value using the given formatter.

impl Default for VerificationStrategy

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for VerificationStrategy

Manual implementation of deserialize due to TOML not supporting “newtype” enum variants. This deserializes using the same parsing rules as FromStr

fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>

where D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl FromStr for VerificationStrategy

This implementation will parse the strategy from a string. MultipleAttestation strategies should be of the format MultipleAttestation[Creator, Approver]

type Err = &'static str

The associated error which can be returned from parsing.

fn from_str(s: &str) -> Result<Self, Self::Err>

Parses a string s to return a value of this type.