SQ(1) User Commands SQ(1) NAME sq-pki-lookup - Lookup the certificates associated with a User ID SYNOPSIS sq pki lookup [OPTIONS] DESCRIPTION Lookup the certificates associated with a User ID. Identifies authenticated bindings (User ID and certificate pairs) where the User ID matches the specified User ID. An error is return if no binding could be authenticated to the specified level (by default: fully authenticated, i.e., a trust amount of 120). 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. OPTIONS Subcommand options --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., this command tries to find 10 paths. --certification-network Treats the network as a certification network Normally, the authentication machinery treats the Web of Trust net- work 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-find- ing algorithms work. --email=EMAIL Find certificates that can be authenticated for the specified email address A certificate is returned if a user ID with the specified email ad- dress can be authenticated for that certificate. To search for a certificate with a user ID containing just the spec- ified email address, use `--userid <EMAIL>`. --gossip 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 authen- ticate a certificate. For instance, imagine Ed wants to authenti- cate 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 certifi- cate. Stable since 1.1.0. --show-paths Show why a binding is authenticated By default, only a user ID and certificate binding's degree of au- thentication (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. --unusable Show bindings that are unusable Normally, unusable certificates and bindings are not shown. This op- tion considers bindings, even if they are not unusable, because they (or the certificates) are not valid according to the policy, are re- voked, or are not live. This option only makes sense with `--gossip`, because unusable bind- ings are still considered unauthenticated. Stable since 1.1.0. --userid=USERID Find certificates that can be authenticated for the specified user ID The specified user ID does not need to be self signed. Global options See sq(1) for a description of the global options. EXAMPLES Lookup certificates that can be authenticated for the given user ID. sq pki lookup --userid "Alice <alice@example.org>" Lookup certificates that have a user ID with the specified email address, and that user ID can be authenticated. sq pki lookup --email alice@example.org SEE ALSO sq(1), sq-pki(1). For the full documentation see <https://book.sequoia-pgp.org/>. VERSION 1.3.1 Sequoia PGP 1.3.1 SQ(1)
Want to link to this manual page? Use this URL:
<https://man.FreeBSD.org/cgi/man.cgi?query=sq-pki-lookup&sektion=1&manpath=FreeBSD+Ports+15.1.quarterly>