SOPV-VERSION(1)
π SOPV-VERSION(1) β Stateless OpenPGP Signature Verification π
okay bestie, welcome to the sopv-version page, aka the "who even am I" page for your Stateless OpenPGP implementation π«Ά
β¨ NAME β¨
sopv-version β get sopv version, build, and compatibility info π
β¨ SYNOPSIS β¨
sopv [--debug] version [--backend|--extended|--sop-spec|--sopv]
β¨ DESCRIPTION β¨
so sopv version is the vibe-check command: it emits version, build, and compatibility information about the specific implementation of sopv you're running. no cap, every implementation is different and this is how you find out which one you've got πΈ
With no options supplied, sopv version produces a single line of text to standard output and exits 0. one line, done, iconic. β¨
That line of output is separated by whitespace into two fields. The first field is the name of the sopv implementation, and the second field is the version number. so like, <name> <version> β that's the whole shape of it π
β¨ EXAMPLES β¨
$ sopv version
ExampleSop 5.2.3
$ sopv version --sopv
1.1
$
look at that. clean. slayed. π₯
β¨ OPTIONS β¨
β οΈ At most one of the following options is allowed. pick one bestie, we can't do all of them π
--backendβ emit a single line describing the primary backend of the tool and its version information. like, which engine is actually doing the work behind the curtain π§--extendedβ emit multiple lines of arbitrary build and configuration information. the first line of output will be the same as the line emitted when runningsopv versionwith no options. and fr fr, this information is always useful when you're submitting a bug report about anysopvimplementation. screenshot it, paste it, send it. the devs will be obsessed π--sop-specβ indicate the targeted version of the sop internet-draft:https://datatracker.ietf.org/doc/draft-dkg-openpgp-stateless-cli/. If the output begins with a~, that indicates the targeted draft is incomplete. yes, the tilde is doing lore duty here π--sopvβ indicate the level of compliance withsopv. If no level ofsopvis fully supported, this will fail withUNSUPPORTED_OPTION. Otherwise, it will emit a level to standard output, like"1.0\n"or"1.1\n". See the VERSION HISTORY section ofsopv(1)for more details π
β¨ RETURN CODE β¨
sopv version returns 0 to indicate success. periodt. β
If the implementation does not understand one of the variants, it will return the non-zero code for UNSUPPORTED_OPTION. so if it claps back with that, it's not being rude, it just doesn't know that option π
β¨ 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 sopv version to learn more about your implementation π«Ά (yes the manpage is telling you to run the command it documents. main character energy honestly π)
β¨ SEE ALSO β¨
sopv(1)sopv-verify(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
and that's the whole page bestie π this is sopv 1.1, dated March 2025 β ty for reading, go run sopv version and find out who you really are π
π
π¦ where this page comes from
- debian trixie: sopv-doc 1.1.1-1 Β· CC0-1.0
- ubuntu resolute: sopv-doc 1.1.1-1 Β· CC0-1.0
- ubuntu stonking: sopv-doc 1.1.1-1 Β· CC0-1.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms