logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

sopv-inline-verify - Verify OpenPGP signed message

Arguments

       One or more CERTS arguments should point to OpenPGP certificates that would be acceptable signers.

Author

       This manual page was written by Daniel Kahn Gillmor. Your implementation of sopv  is  likely  written  by
       someone  else  in  alignment with the SOP specification. Please run sopvversion to learn more about your
       implementation.

Description

sopvinline-verify evaluates OpenPGP signatures bundled in a message. Its standard input can be either  a
       OpenPGP  Signed  Message  or  a  message  signed with the OpenPGP Cleartext Signing Framework. If a valid
       signature is found, it returns 0 and emits the contents  of  the  message  (without  any  signatures)  on
       standard output.

       If no valid OpenPGP signature is found, sopvinline-verify returns non-zero.

Examples

       if sopv inline-verify signer.cert < message.signed > message.txt; then
           echo "The information found in message.txt was signed"
       else
           rm message.txt
           echo "no valid signature found"
       fi

Name

sopv-inline-verify - Verify OpenPGP signed message

Options

--not-before=DATE
              Do  not  accept  signatures  made  before  the  specified  DATE.  Supply  DATE in ISO-8601 format,
              preferably in UTC (see DATE in sopv(1)).

       --not-after=DATE
              Do not accept signatures made after the specified DATE. Supply DATE in ISO-8601 format, preferably
              in UTC (see DATE in sopv(1)).

       --verifications-out=VERIFICATIONS
              If the caller wants to inspect the details of the valid signatures, it can use  this  argument  to
              request those details. See VERIFICATIONS in sopv(1) for more details about this format.

Return Code

sopvinline-verify returns 0 to to indicate that at least one valid signature was found.

       It  may fail for other reason, but NO_SIGNATURE (3) is a likely failure mode when the message contains no
       valid signature from any of the CERTS.

See Also

sopv(1),   sopv-version(1),   sopv-inline-verify(1),   Stateless   OpenPGP   Command    Line    Interface
       https://datatracker.ietf.org/doc/draft-dkg-openpgp-stateless-cli/,                RFC                9580
       https://www.rfc-editor.org/rfc/rfc9580.html

sopv 1.1                                          February 2025                            SOPV-INLINE-VERIFY(1)

Synopsis

sopv  [--debug]  inline-verify [--not-before=DATE] [--not-after=DATE] [--verifications-out=VERIFICATIONS]
       [--] CERTS [CERTS...] <INLINESIGNED

See Also