keylookup(1)

1keylookup(1)                                                      keylookup(1)
2
3
4

NAME

6       keylookup - Fetch and Import GnuPG keys from keyservers.
7
8

SYNOPSIS

10       keylookup [options] search-string
11
12

DESCRIPTION

14       keylookup  is a wrapper around gpg --search, allowing you to search for
15       keys on a keyserver.  It presents the list of matching keys to the user
16       and allows her to select the keys for importing into the GnuPG keyring.
17
18       For the search and actual import of keys GnuPG itself is called.
19
20
21

OPTIONS

23       --keyserver=keyserver
24               Specify  the keyserver to use. If no keyserver is specified, it
25               will parse the GnuPG options file for a  default  keyserver  to
26               use.  If no keyserver can be found, keylookup will abort.
27
28
29       --port=port
30               Use a port other than 11371.
31
32
33       --frontend=frontend
34               keylookup supports displaying the search results with 3 differ‐
35               ent frondends. Both whiptail and  dialog  are  interactive  and
36               allow  the  user to select the keys to import.  The third fron‐
37               tend plain is non-interactive and just prints the keys to  STD‐
38               OUT. The user must then call GnuPG him/herself.
39
40               If  available,  /usr/bin/dialog  is  the  default. If it is not
41               available but /usr/bin/whiptail is installed, then this is used
42               instead. If nothing else works, we'll fall back to plain.
43
44
45       --importall
46               Don't ask the user which keys to import, but instead import all
47               keys matching the search-string. If this is given  no  frontend
48               is needed.
49
50
51       --honor-http-proxy
52               Similar  to GnuP keylookup will only honor the http_proxy envi‐
53               ronment variable if this option is given. If it  is  not  given
54               but  your  GnuPG  options file includes it, then keylookup will
55               use it.
56
57
58       --help  Print a brief help message and exit successfully.
59
60
61
62

ENVIRONMENT

64       HOME      Used to locate the default home directory.
65
66
67       GNUPGHOME If set directory used instead of "~/.gnupg".
68
69
70       GNUPGBIN  If set used as gpg binary instead of "gpg".
71
72
73       http_proxy
74                 Only honored when the option  --honor-http-proxy  is  set  or
75                 honor-http-proxy is set in GnuPG's config file.
76
77
78
79

EXAMPLES

81       keylookup Christian Kurz
82              will query your default keyserver for Christian's keys and offer
83              you to import them into your keyring with  the  dialog  frontend
84              (if available).
85
86
87       keylookup --honor-http-proxy --frontend plain wk@gnupg
88              will query the default keyserver again, now using the http_proxy
89              if the environment variable is defined and list wk@gnupg's (Wer‐
90              ner Koch)'s key on STDOUT.
91
92
93       keylookup --keyserver pgp.mit.edu Peter Palfrader
94              will now ask the keyserver pgp.mit.edu for my (Peter's) keys and
95              display them for import in dialog.
96
97
98

FILES

100       ~/.gnupg/options
101                 GnuPG's options file where keylookup will take the  keyserver
102                 and honor-http-proxy values from if it exists.
103
104
105

BUGS

111       Please   report   bugs   using   the  Debian  bug  tracking  system  at
112       https://bugs.debian.org/.
113
114
115

AUTHORS

117       Christian Kurz <shorty@debian.org>
118       Peter Palfrader <peter@palfrader.org>
119
120
121
122Jun-2002                                                          keylookup(1)