Your company here — click to reach over 10,000 unique daily visitors

sq-pki-list - Man Page

List all authenticated bindings (User ID and certificate pairs)


sq pki list [Options] PATTERN


List all authenticated bindings (User ID and certificate pairs).

Only bindings that meet the specified trust amount (by default bindings that are fully authenticated, i.e., have a trust amount of 120), are shown.

Even if no bindings are shown, the exit status is 0.

If `--email` is provided, then a pattern matches if it is a case insensitive substring of the email address as-is or the normalized email address.  Note: unlike the email address, the pattern is not normalized.  In particular, puny code normalization is not done on the pattern.


Subcommand options

-a, --amount=AMOUNT

The required amount of trust.

120 indicates full authentication; values less than 120 indicate partial authentication.  When `--certification-network` is passed, this defaults to 1200, i.e., `sq pki` tries to find 10 paths.


Treats the network as a certification network.

Normally, `sq pki` treats the Web of Trust network as an authentication network where a certification only means that the binding is correct, not that the target should be treated as a trusted introducer.  In a certification network, the targets of certifications are treated as trusted introducers with infinite depth, and any regular expressions are ignored. Note: The trust amount remains unchanged.  This is how most so-called PGP path-finding algorithms work.


Changes the USERID parameter 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.

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.


Treats all certificates as unreliable trust roots.

This option is useful for figuring out what others think about a certificate (i.e., gossip or hearsay).  In other words, this finds arbitrary paths to a particular certificate.

Gossip is useful in helping to identify alternative ways to authenticate a certificate.  For instance, imagine Ed wants to authenticate Laura's certificate, but asking her directly is inconvenient.  Ed discovers that Micah has certified Laura's certificate, but Ed hasn't yet authenticated Micah's certificate.  If Ed is willing to rely on Micah as a trusted introducer, and authenticating Micah's certificate is easier than authenticating Laura's certificate, then Ed has learned about an easier way to authenticate Laura's certificate.


Show why a binding is authenticated.

By default, only a user ID and certificate binding's degree of authentication (a value between 0 and 120) is shown.  This changes the output to also show how that value was computed by showing the paths from the trust roots to the bindings.


A pattern to select the bindings to authenticate.

The pattern is treated as a UTF-8 encoded string and a case insensitive substring search (using the current locale) is performed against each User ID.  If a User ID is not valid UTF-8, the binding is ignored.

Global options

See sq(1) for a description of the global options.


List all bindings for user IDs containing an email address from example.org, and that can be authenticated.

    sq pki list @example.org

See Also

sq(1), sq-pki(1).

For the full documentation see <https://book.sequoia-pgp.org>.


0.37.0 (sequoia-openpgp 1.21.1)

Referenced By


0.37.0 Sequoia PGP