Overview

This node operation verifies the authenticity of a message or binary data using PGP (Pretty Good Privacy) signatures. It supports verifying both text and binary inputs, ensuring that the message or data has not been tampered with and is from a trusted source. This is useful in scenarios where secure communication and data integrity are critical, such as verifying signed emails, documents, or files.

Use Case Examples

1. Verifying a signed text message to confirm the sender's identity.
2. Verifying a binary file's signature to ensure it has not been altered after signing.

Properties

Name	Meaning
Input Type	Specifies whether the input to verify is text or binary data.
Message	The text message to verify (used when input type is text).
Binary Property Name	The name of the binary property containing the data to verify (used when input type is binary).
Signature	The PGP signature string to verify against the message (used when input type is text and signature is not embedded).
Binary Property Name (Signature)	The name of the binary property containing the signature to verify (used when input type is binary and signature is not embedded).

Output

JSON

• verified - Boolean indicating whether the signature verification was successful.

Dependencies

• Requires PGP credentials including a private key, public key, and optionally a passphrase for the private key.

Troubleshooting

• Common errors include invalid or malformed private/public keys, which will cause the node to throw errors indicating the keys are not valid.
• If the message or binary data cannot be decrypted or verified, the node throws errors such as 'Message could not be decrypted' or 'Message could not be uncompressed'. These can be resolved by ensuring the correct keys and compression algorithms are used.
• If the specified binary property or signature property is missing, the node throws errors indicating the missing binary data. Ensure the correct property names are provided.