1 # These first three lines are not copied to the gpg.conf file in
2 # the users home directory.
5 # Copyright 1998, 1999, 2000, 2001, 2002, 2003,
6 # 2010 Free Software Foundation, Inc.
8 # This file is free software; as a special exception the author gives
9 # unlimited permission to copy and/or distribute it, with or without
10 # modifications, as long as this notice is preserved.
12 # This file is distributed in the hope that it will be useful, but
13 # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
14 # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
16 # Unless you specify which option file to use (with the command line
17 # option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf
20 # An options file can contain any long options which are available in
21 # GnuPG. If the first non white space character of a line is a '#',
22 # this line is ignored. Empty lines are also ignored.
24 # See the man page for a list of options.
26 # Uncomment the following option to get rid of the copyright notice
30 # If you have more than 1 secret key in your keyring, you may want to
31 # uncomment the following option and set your preferred keyid.
35 # If you do not pass a recipient to gpg, it will ask for one. Using
36 # this option you can encrypt to a default key. Key validation will
37 # not be done in this case. The second form uses the default key as
40 #default-recipient some-user-id
41 #default-recipient-self
43 # By default GnuPG creates version 4 signatures for data files as
44 # specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP
45 # require the older version 3 signatures. Setting this option forces
46 # GnuPG to create version 3 signatures.
50 # Because some mailers change lines starting with "From " to ">From "
51 # it is good to handle such lines in a special way when creating
52 # cleartext signatures; all other PGP versions do it this way too.
53 # To enable full OpenPGP compliance you may want to use this option.
57 # When verifying a signature made from a subkey, ensure that the cross
58 # certification "back signature" on the subkey is present and valid.
59 # This protects against a subtle attack against subkeys that can sign.
60 # Defaults to --no-require-cross-certification. However for new
61 # installations it should be enabled.
63 require-cross-certification
66 # If you do not use the Latin-1 (ISO-8859-1) charset, you should tell
67 # GnuPG which is the native character set. Please check the man page
68 # for supported character sets. This character set is only used for
69 # metadata and not for the actual message which does not undergo any
70 # translation. Note that future version of GnuPG will change to UTF-8
71 # as default character set.
75 # Group names may be defined like this:
76 # group mynames = paige 0x12345678 joe patti
78 # Any time "mynames" is a recipient (-r or --recipient), it will be
79 # expanded to the names "paige", "joe", and "patti", and the key ID
80 # "0x12345678". Note there is only one level of expansion - you
81 # cannot make an group that points to another group. Note also that
82 # if there are spaces in the recipient name, this will appear as two
83 # recipients. In these cases it is better to use the key ID.
85 #group mynames = paige 0x12345678 joe patti
87 # Some old Windows platforms require 8.3 filenames. If your system
88 # can handle long filenames, uncomment this.
90 #no-mangle-dos-filenames
92 # Lock the file only once for the lifetime of a process. If you do
93 # not define this, the lock will be obtained and released every time
94 # it is needed - normally this is not needed.
98 # GnuPG can send and receive keys to and from a keyserver. These
99 # servers can be HKP, email, or LDAP (if GnuPG is built with LDAP
102 # Example HKP keyservers:
103 # hkp://keys.gnupg.net
105 # Example LDAP keyservers:
106 # ldap://pgp.surfnet.nl:11370
108 # Regular URL syntax applies, and you can set an alternate port
109 # through the usual method:
110 # hkp://keyserver.example.net:22742
112 # If you have problems connecting to a HKP server through a buggy http
113 # proxy, you can use keyserver option broken-http-proxy (see below),
114 # but first you should make sure that you have read the man page
115 # regarding proxies (keyserver option honor-http-proxy)
117 # Most users just set the name and type of their preferred keyserver.
118 # Note that most servers (with the notable exception of
119 # ldap://keyserver.pgp.com) synchronize changes with each other. Note
120 # also that a single server name may actually point to multiple
121 # servers via DNS round-robin. hkp://keys.gnupg.net is an example of
122 # such a "server", which spreads the load over a number of physical
123 # servers. To see the IP address of the server actually used, you may use
124 # the "--keyserver-options debug".
126 keyserver hkp://keys.gnupg.net
127 #keyserver http://http-keys.gnupg.net
128 #keyserver mailto:pgp-public-keys@keys.nl.pgp.net
130 # Common options for keyserver functions:
132 # include-disabled = when searching, include keys marked as "disabled"
133 # on the keyserver (not all keyservers support this).
135 # no-include-revoked = when searching, do not include keys marked as
136 # "revoked" on the keyserver.
138 # verbose = show more information as the keys are fetched.
139 # Can be used more than once to increase the amount
140 # of information shown.
142 # use-temp-files = use temporary files instead of a pipe to talk to the
143 # keyserver. Some platforms (Win32 for one) always
146 # keep-temp-files = do not delete temporary files after using them
147 # (really only useful for debugging)
149 # honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy
150 # environment variable
152 # broken-http-proxy = try to work around a buggy HTTP proxy
154 # auto-key-retrieve = automatically fetch keys as needed from the keyserver
155 # when verifying signatures or when importing keys that
156 # have been revoked by a revocation key that is not
157 # present on the keyring.
159 # no-include-attributes = do not include attribute IDs (aka "photo IDs")
160 # when sending keys to the keyserver.
162 #keyserver-options auto-key-retrieve
164 # Uncomment this line to display photo user IDs in key listings and
165 # when a signature from a key with a photo is verified.
169 # Use this program to display photo user IDs
171 # %i is expanded to a temporary file that contains the photo.
172 # %I is the same as %i, but the file isn't deleted afterwards by GnuPG.
173 # %k is expanded to the key ID of the key.
174 # %K is expanded to the long OpenPGP key ID of the key.
175 # %t is expanded to the extension of the image (e.g. "jpg").
176 # %T is expanded to the MIME type of the image (e.g. "image/jpeg").
177 # %f is expanded to the fingerprint of the key.
178 # %% is %, of course.
180 # If %i or %I are not present, then the photo is supplied to the
181 # viewer on standard input. If your platform supports it, standard
182 # input is the best way to do this as it avoids the time and effort in
183 # generating and then cleaning up a secure temp file.
185 # The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin"
186 # On Mac OS X and Windows, the default is to use your regular JPEG image
189 # Some other viewers:
190 # photo-viewer "qiv %i"
191 # photo-viewer "ee %i"
192 # photo-viewer "display -title 'KeyID 0x%k'"
194 # This one saves a copy of the photo ID in your home directory:
195 # photo-viewer "cat > ~/photoid-for-key-%k.%t"
197 # Use your MIME handler to view photos:
198 # photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG"