Interface SignatureOrBuilder (2.74.0)

  public 
  
 interface 
 SignatureOrBuilder 
  
 extends 
  
 MessageOrBuilder 
 

  public 
  
 abstract 
  
 String 
  
 getPublicKeyId 
 () 
 

The identifier for the public key that verifies this signature.

• The public_key_id is required.
• The public_key_id SHOULD be an RFC3986 conformant URI.

• When possible, the public_key_id SHOULD be an immutable reference, such as a cryptographic digest.

  Examples of valid public_key_id s:

  OpenPGP V4 public key fingerprint:

• "openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA" See https://www.iana.org/assignments/uri-schemes/prov/openpgp4fpr for more details on this scheme.

  RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization):

• "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU"
• "nih:///sha-256;703f68f42aba2c6de30f488a5ea122fef76324679c9bf89791ba95a1271589a5"

string public_key_id = 2;

  public 
  
 abstract 
  
 ByteString 
  
 getPublicKeyIdBytes 
 () 
 

The identifier for the public key that verifies this signature.

• The public_key_id is required.
• The public_key_id SHOULD be an RFC3986 conformant URI.

• When possible, the public_key_id SHOULD be an immutable reference, such as a cryptographic digest.

  Examples of valid public_key_id s:

  OpenPGP V4 public key fingerprint:

• "openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA" See https://www.iana.org/assignments/uri-schemes/prov/openpgp4fpr for more details on this scheme.

  RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization):

• "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU"
• "nih:///sha-256;703f68f42aba2c6de30f488a5ea122fef76324679c9bf89791ba95a1271589a5"

string public_key_id = 2;

  public 
  
 abstract 
  
 ByteString 
  
 getSignature 
 () 
 

The content of the signature, an opaque bytestring. The payload that this signature verifies MUST be unambiguously provided with the Signature during verification. A wrapper message might provide the payload explicitly. Alternatively, a message might have a canonical serialization that can always be unambiguously computed to derive the payload.

bytes signature = 1;