lookup(1)
π lookup(1) β the vibe check for your certificates π
okay bestie, pull up a chair π«Ά this is the manual page for lookup, from the General Commands Manual, section 1. It's giving "who even is this person and do I trust them" energy, and honestly? iconic.
β¨ NAME β¨
lookup β Lookup the certificates associated with a User ID
πΈ SYNOPSIS πΈ
lookup [--email] [-h|--help] <USERID>
π¦ DESCRIPTION π¦
Lookup the certificates associated with a User ID. That's the whole gig, no cap. π
It identifies authenticated bindings β that's User ID and certificate pairs, bestie, they come as a duo β where the User ID matches the User ID you specified.
If a binding could be authenticated to the specified level (by default: fully authenticated, i.e., a trust amount of 120), then the exit status is 0. Otherwise the exit status is 1. Slay or don't slay, those are the options. π
If a binding could be partially authenticated (i.e., its trust amount is greater than 0), then the binding is displayed, even if the trust is below the specified threshold. Not me being generous with the receipts β¨
π OPTIONS π
--emailβ Changes theUSERIDparameter to match User IDs with the specified email address.
Interprets the USERID parameter as an email address, which is then used to select User IDs with that email address.
Unlike when comparing User IDs, email addresses are first normalized by the domain to ASCII using IDNA2008 Punycode conversion, and then converting the resulting email address to lowercase using the empty locale. yes it's a whole glow-up routine, let it cook π§
If multiple User IDs match, they are each considered in turn, and this function returns success if at least one of those User IDs can be authenticated. Note: The paths to the different User IDs are not combined. no merging, no blending, they stay separate, periodt π
-h,--helpβ Print help (see a summary with'-h')<USERID>β The User ID to authenticate.
This is case sensitive, and must be the whole User ID, not just a substring or an email address. fr fr, no half-sending, no vibes-based guessing π
π EXTRA π
EXAMPLES:
# Lookup a certificate with the given User ID.
$ sq-wot --keyring keyring.pgp \
--partial \
--trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
lookup \
'Alice <alice@example.org>'
# The same as above, but output in DOT format and convert it to
# an SVG using Graphviz's DOT compiler.
$ sq-wot --format dot \
--keyring keyring.pgp \
--partial \
--trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
lookup \
'Alice <alice@example.org>' \
| dot -Tsvg -o alice.svg
# Lookup a certificate with the given email address.
$ sq-wot --keyring keyring.pgp \
--trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
lookup \
--email 'alice@example.org'
# The same as above, but output in DOT format and convert it to
# an SVG using Graphviz's DOT compiler.
$ sq-wot --format dot \
--keyring keyring.pgp \
--trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
lookup \
--email 'alice@example.org' \
| dot -Tsvg -o alice.svg
okay that's the whole page, you ate it up π π this lil manual is the lookup page from the General Commands Manual (section 1), so go forth and authenticate your people, bestie πΈπ¦β¨
π¦ where this page comes from
- ubuntu noble: sq-wot 0.11.0-1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms