Debian Codegraph @

autotests/gnupg_home/gpg.conf

raw
1 # Options for GnuPG
2 # SPDX-FileCopyrightText: 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
3 # SPDX-License-Identifier: FSFULLR
4 #
5 # Unless you specify which option file to use (with the command line
6 # option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf
7 # by default.
8 #
9 # An options file can contain any long options which are available in
10 # GnuPG. If the first non white space character of a line is a '#',
11 # this line is ignored. Empty lines are also ignored.
12 #
13 # See the man page for a list of options.
14
15 # Uncomment the following option to get rid of the copyright notice
16
17 #no-greeting
18
19 # If you have more than 1 secret key in your keyring, you may want to
20 # uncomment the following option and set your preferred keyid.
21
22 #default-key 621CC013
23
24 # If you do not pass a recipient to gpg, it will ask for one. Using
25 # this option you can encrypt to a default key. Key validation will
26 # not be done in this case. The second form uses the default key as
27 # default recipient.
28
29 #default-recipient some-user-id
30 #default-recipient-self
31
32 # Use --encrypt-to to add the specified key as a recipient to all
33 # messages. This is useful, for example, when sending mail through a
34 # mail client that does not automatically encrypt mail to your key.
35 # In the example, this option allows you to read your local copy of
36 # encrypted mail that you've sent to others.
37
38 #encrypt-to some-key-id
39
40 # By default GnuPG creates version 3 signatures for data files. This
41 # is not strictly OpenPGP compliant but PGP 6 and most versions of PGP
42 # 7 require them. To disable this behavior, you may use this option
43 # or --openpgp.
44
45 #no-force-v3-sigs
46
47 # Because some mailers change lines starting with "From " to ">From "
48 # it is good to handle such lines in a special way when creating
49 # cleartext signatures; all other PGP versions do it this way too.
50
51 #no-escape-from-lines
52
53 # If you do not use the Latin-1 (ISO-8859-1) charset, you should tell
54 # GnuPG which is the native character set. Please check the man page
55 # for supported character sets. This character set is only used for
56 # metadata and not for the actual message which does not undergo any
57 # translation. Note that future version of GnuPG will change to UTF-8
58 # as default character set. In most cases this option is not required
59 # as GnuPG is able to figure out the correct charset at runtime.
60
61 #charset utf-8
62
63 # Group names may be defined like this:
64 # group mynames = paige 0x12345678 joe patti
65 #
66 # Any time "mynames" is a recipient (-r or --recipient), it will be
67 # expanded to the names "paige", "joe", and "patti", and the key ID
68 # "0x12345678". Note there is only one level of expansion - you
69 # cannot make an group that points to another group. Note also that
70 # if there are spaces in the recipient name, this will appear as two
71 # recipients. In these cases it is better to use the key ID.
72
73 #group mynames = paige 0x12345678 joe patti
74
75 # Lock the file only once for the lifetime of a process. If you do
76 # not define this, the lock will be obtained and released every time
77 # it is needed, which is usually preferable.
78
79 #lock-once
80
81 # GnuPG can send and receive keys to and from a keyserver. These
82 # servers can be HKP, email, or LDAP (if GnuPG is built with LDAP
83 # support).
84 #
85 # Example HKP keyserver:
86 # hkp://keys.gnupg.net
87 # hkp://subkeys.pgp.net
88 #
89 # Example email keyserver:
90 # mailto:[email protected]
91 #
92 # Example LDAP keyservers:
93 # ldap://keyserver.pgp.com
94 #
95 # Regular URL syntax applies, and you can set an alternate port
96 # through the usual method:
97 # hkp://keyserver.example.net:22742
98 #
99 # Most users just set the name and type of their preferred keyserver.
100 # Note that most servers (with the notable exception of
101 # ldap://keyserver.pgp.com) synchronize changes with each other. Note
102 # also that a single server name may actually point to multiple
103 # servers via DNS round-robin. hkp://keys.gnupg.net is an example of
104 # such a "server", which spreads the load over a number of physical
105 # servers. To see the IP address of the server actually used, you may use
106 # the "--keyserver-options debug".
107
108 keyserver hkp://keys.gnupg.net
109 #keyserver mailto:[email protected]
110 #keyserver ldap://keyserver.pgp.com
111
112 # Common options for keyserver functions:
113 #
114 # include-disabled : when searching, include keys marked as "disabled"
115 # on the keyserver (not all keyservers support this).
116 #
117 # no-include-revoked : when searching, do not include keys marked as
118 # "revoked" on the keyserver.
119 #
120 # verbose : show more information as the keys are fetched.
121 # Can be used more than once to increase the amount
122 # of information shown.
123 #
124 # use-temp-files : use temporary files instead of a pipe to talk to the
125 # keyserver. Some platforms (Win32 for one) always
126 # have this on.
127 #
128 # keep-temp-files : do not delete temporary files after using them
129 # (really only useful for debugging)
130 #
131 # http-proxy="proxy" : set the proxy to use for HTTP and HKP keyservers.
132 # This overrides the "http_proxy" environment variable,
133 # if any.
134 #
135 # auto-key-retrieve : automatically fetch keys as needed from the keyserver
136 # when verifying signatures or when importing keys that
137 # have been revoked by a revocation key that is not
138 # present on the keyring.
139 #
140 # no-include-attributes : do not include attribute IDs (aka "photo IDs")
141 # when sending keys to the keyserver.
142
143 #keyserver-options auto-key-retrieve
144
145 # Display photo user IDs in key listings
146
147 # list-options show-photos
148
149 # Display photo user IDs when a signature from a key with a photo is
150 # verified
151
152 # verify-options show-photos
153
154 # Use this program to display photo user IDs
155 #
156 # %i is expanded to a temporary file that contains the photo.
157 # %I is the same as %i, but the file isn't deleted afterwards by GnuPG.
158 # %k is expanded to the key ID of the key.
159 # %K is expanded to the long OpenPGP key ID of the key.
160 # %t is expanded to the extension of the image (e.g. "jpg").
161 # %T is expanded to the MIME type of the image (e.g. "image/jpeg").
162 # %f is expanded to the fingerprint of the key.
163 # %% is %, of course.
164 #
165 # If %i or %I are not present, then the photo is supplied to the
166 # viewer on standard input. If your platform supports it, standard
167 # input is the best way to do this as it avoids the time and effort in
168 # generating and then cleaning up a secure temp file.
169 #
170 # If no photo-viewer is provided, GnuPG will look for xloadimage, eog,
171 # or display (ImageMagick). On Mac OS X and Windows, the default is
172 # to use your regular JPEG image viewer.
173 #
174 # Some other viewers:
175 # photo-viewer "qiv %i"
176 # photo-viewer "ee %i"
177 #
178 # This one saves a copy of the photo ID in your home directory:
179 # photo-viewer "cat > ~/photoid-for-key-%k.%t"
180 #
181 # Use your MIME handler to view photos:
182 # photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG"
183
184 # Passphrase agent
185 #
186 # We support the old experimental passphrase agent protocol as well as
187 # the new Assuan based one (currently available in the "newpg" package
188 # at ftp.gnupg.org/gcrypt/alpha/aegypten/). To make use of the agent,
189 # you have to run an agent as daemon and use the option
190 #
191 # use-agent
192 #
193 # which tries to use the agent but will fallback to the regular mode
194 # if there is a problem connecting to the agent. The normal way to
195 # locate the agent is by looking at the environment variable
196 # GPG_AGENT_INFO which should have been set during gpg-agent startup.
197 # In certain situations the use of this variable is not possible, thus
198 # the option
199 #
200 # --gpg-agent-info=<path>:<pid>:1
201 #
202 # may be used to override it.
203
204 # Automatic key location
205 #
206 # GnuPG can automatically locate and retrieve keys as needed using the
207 # auto-key-locate option. This happens when encrypting to an email
208 # address (in the "[email protected]" form), and there are no
209 # [email protected] keys on the local keyring. This option takes the
210 # following arguments, in the order they are to be tried:
211 #
212 # cert = locate a key using DNS CERT, as specified in RFC-4398.
213 # GnuPG can handle both the PGP (key) and IPGP (URL + fingerprint)
214 # CERT methods.
215 #
216 # pka = locate a key using DNS PKA.
217 #
218 # ldap = locate a key using the PGP Universal method of checking
219 # "ldap://keys.(thedomain)". For example, encrypting to
220 # [email protected] will check ldap://keys.example.com.
221 #
222 # keyserver = locate a key using whatever keyserver is defined using
223 # the keyserver option.
224 #
225 # You may also list arbitrary keyservers here by URL.
226 #
227 # Try CERT, then PKA, then LDAP, then hkp://subkeys.net:
228 #auto-key-locate cert pka ldap hkp://subkeys.pgp.net
229
230 ###+++--- GPGConf ---+++###
231 utf8-strings
232 #debug-level basic
233 #log-file socket:///home/leo/kde/src/kdepim/messagecomposer/tests/gnupg_home/log-socket
234 ###+++--- GPGConf ---+++### Tue 29 Jun 2010 10:23:13 AM EDT
235 # GPGConf edited this configuration file.
236 # It will disable options before this marked block, but it will
237 # never change anything below these lines.