1
# help.txt - English GnuPG online help
2
# Copyright (C) 2007 Free Software Foundation, Inc.
4
# This file is part of GnuPG.
6
# GnuPG is free software; you can redistribute it and/or modify
7
# it under the terms of the GNU General Public License as published by
8
# the Free Software Foundation; either version 3 of the License, or
9
# (at your option) any later version.
11
# GnuPG is distributed in the hope that it will be useful,
12
# but WITHOUT ANY WARRANTY; without even the implied warranty of
13
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14
# GNU General Public License for more details.
16
# You should have received a copy of the GNU General Public License
17
# along with this program; if not, see <http://www.gnu.org/licenses/>.
20
# Note that this help file needs to be UTF-8 encoded. When looking
21
# for a help item, GnuPG scans the help files in the following order
22
# (assuming a GNU or Unix system):
24
# /etc/gnupg/help.LL_TT.txt
25
# /etc/gnupg/help.LL.txt
27
# /usr/share/gnupg/help.LL_TT.txt
28
# /usr/share/gnupg/help.LL.txt
29
# /usr/share/gnupg/help.txt
31
# Here LL_TT denotes the full name of the current locale with the
32
# territory (.e.g. "de_DE"), LL denotes just the locale name
33
# (e.g. "de"). The first matching item is returned. To put a dot or
34
# a hash mark at the beginning of a help text line, it needs to be
35
# prefixed with ". ". A single dot may be used to terminated ahelp
38
.#pinentry.qualitybar.tooltip
39
# [remove the hash mark from the key to enable this text]
40
# This entry is just an example on how to customize the tooltip shown
41
# when hovering over the quality bar of the pinentry. We don't
42
# install this text so that the hardcoded translation takes
43
# precedence. An administrator should write up a short help to tell
44
# the users about the configured passphrase constraints and save that
45
# to /etc/gnupg/help.txt. The help text should not be longer than
46
# about 800 characters.
47
This bar indicates the quality of the passphrase entered above.
49
As long as the bar is shown in red, GnuPG considers the passphrase too
50
weak to accept. Please ask your administrator for details about the
51
configured passphrase constraints.
56
# There was a problem accessing or starting the agent.
57
It was either not possible to connect to a running Gpg-Agent or a
58
communication problem with a running agent occurred.
60
The system uses a background process, called Gpg-Agent, for processing
61
private keys and to ask for passphrases. The agent is usually started
62
when the user logs in and runs as long the user is logged in. In case
63
that no agent is available, the system tries to start one on the fly
64
but that version of the agent is somewhat limited in functionality and
65
thus may lead to little problems.
67
You probably need to ask your administrator on how to solve the
68
problem. As a workaround you might try to log out and in to your
69
session and see whether this helps. If this helps please tell the
70
administrator anyway because this indicates a bug in the software.
74
.gnupg.dirmngr-problem
75
# There was a problen accessing the dirmngr.
76
It was either not possible to connect to a running Dirmngr or a
77
communication problem with a running Dirmngr occurred.
79
To lookup certificate revocation lists (CRLs), performing OCSP
80
validation and to lookup keys through LDAP servers, the system uses an
81
external service program named Dirmngr. The Dirmngr is usually running
82
as a system service (daemon) and does not need any attention by the
83
user. In case of problems the system might start its own copy of the
84
Dirmngr on a per request base; this is a workaround and yields limited
87
If you encounter this problem, you should ask your system
88
administrator how to proceed. As an interim solution you may try to
89
disable CRL checking in gpgsm's configuration.
93
.gpg.edit_ownertrust.value
94
# The help identies prefixed with "gpg." used to be hard coded in gpg
95
# but may now be overridden by help texts from this file.
96
It's up to you to assign a value here; this value will never be exported
97
to any 3rd party. We need it to implement the web-of-trust; it has nothing
98
to do with the (implicitly created) web-of-certificates.
101
.gpg.edit_ownertrust.set_ultimate.okay
102
To build the Web-of-Trust, GnuPG needs to know which keys are
103
ultimately trusted - those are usually the keys for which you have
104
access to the secret key. Answer "yes" to set this key to
108
.gpg.untrusted_key.override
109
If you want to use this untrusted key anyway, answer "yes".
112
.gpg.pklist.user_id.enter
113
Enter the user ID of the addressee to whom you want to send the message.
117
Select the algorithm to use.
119
DSA (aka DSS) is the Digital Signature Algorithm and can only be used
122
Elgamal is an encrypt-only algorithm.
124
RSA may be used for signatures or encryption.
126
The first (primary) key must always be a key which is capable of signing.
130
.gpg.keygen.algo.rsa_se
131
In general it is not a good idea to use the same key for signing and
132
encryption. This algorithm should only be used in certain domains.
133
Please consult your security expert first.
138
Enter the size of the key.
141
.gpg.keygen.size.huge.okay
142
Answer "yes" or "no".
146
.gpg.keygen.size.large.okay
147
Answer "yes" or "no".
152
Enter the required value as shown in the prompt.
153
It is possible to enter a ISO date (YYYY-MM-DD) but you won't
154
get a good error response - instead the system tries to interpret
155
the given value as an interval.
158
.gpg.keygen.valid.okay
159
Answer "yes" or "no".
164
Enter the name of the key holder.
169
Please enter an optional but highly suggested email address.
173
Please enter an optional comment.
177
.gpg.keygen.userid.cmd
178
# (Keep a leading empty line)
180
N to change the name.
181
C to change the comment.
182
E to change the email address.
183
O to continue with key generation.
184
Q to to quit the key generation.
188
Answer "yes" (or just "y") if it is okay to generate the sub key.
192
Answer "yes" or "no".
196
When you sign a user ID on a key, you should first verify that the key
197
belongs to the person named in the user ID. It is useful for others to
198
know how carefully you verified this.
200
"0" means you make no particular claim as to how carefully you verified the
203
"1" means you believe the key is owned by the person who claims to own it
204
but you could not, or did not verify the key at all. This is useful for
205
a "persona" verification, where you sign the key of a pseudonymous user.
207
"2" means you did casual verification of the key. For example, this could
208
mean that you verified the key fingerprint and checked the user ID on the
209
key against a photo ID.
211
"3" means you did extensive verification of the key. For example, this could
212
mean that you verified the key fingerprint with the owner of the key in
213
person, and that you checked, by means of a hard to forge document with a
214
photo ID (such as a passport) that the name of the key owner matches the
215
name in the user ID on the key, and finally that you verified (by exchange
216
of email) that the email address on the key belongs to the key owner.
218
Note that the examples given above for levels 2 and 3 are *only* examples.
219
In the end, it is up to you to decide just what "casual" and "extensive"
220
mean to you when you sign other keys.
222
If you don't know what the right answer is, answer "0".
225
.gpg.change_passwd.empty.okay
226
Answer "yes" or "no".
230
.gpg.keyedit.save.okay
231
Answer "yes" or "no".
235
.gpg.keyedit.cancel.okay
236
Answer "yes" or "no".
239
.gpg.keyedit.sign_all.okay
240
Answer "yes" if you want to sign ALL the user IDs.
243
.gpg.keyedit.remove.uid.okay
244
Answer "yes" if you really want to delete this user ID.
245
All certificates are then also lost!
248
.gpg.keyedit.remove.subkey.okay
249
Answer "yes" if it is okay to delete the subkey.
253
.gpg.keyedit.delsig.valid
254
This is a valid signature on the key; you normally don't want
255
to delete this signature because it may be important to establish a
256
trust connection to the key or another key certified by this key.
259
.gpg.keyedit.delsig.unknown
260
This signature can't be checked because you don't have the
261
corresponding key. You should postpone its deletion until you
262
know which key was used because this signing key might establish
263
a trust connection through another already certified key.
266
.gpg.keyedit.delsig.invalid
267
The signature is not valid. It does make sense to remove it from
271
.gpg.keyedit.delsig.selfsig
272
This is a signature which binds the user ID to the key. It is
273
usually not a good idea to remove such a signature. Actually
274
GnuPG might not be able to use this key anymore. So do this
275
only if this self-signature is for some reason not valid and
276
a second one is available.
279
.gpg.keyedit.updpref.okay
280
Change the preferences of all user IDs (or just of the selected ones)
281
to the current list of preferences. The timestamp of all affected
282
self-signatures will be advanced by one second.
286
.gpg.passphrase.enter
287
# (keep a leading empty line)
289
Please enter the passhrase; this is a secret sentence.
293
.gpg.passphrase.repeat
294
Please repeat the last passphrase, so you are sure what you typed in.
297
.gpg.detached_signature.filename
298
Give the name of the file to which the signature applies.
301
.gpg.openfile.overwrite.okay
302
# openfile.c (overwrite_filep)
303
Answer "yes" if it is okay to overwrite the file.
306
.gpg.openfile.askoutname
307
# openfile.c (ask_outfile_name)
308
Please enter a new filename. If you just hit RETURN the default
309
file (which is shown in brackets) will be used.
312
.gpg.ask_revocation_reason.code
313
# revoke.c (ask_revocation_reason)
314
You should specify a reason for the certification. Depending on the
315
context you have the ability to choose from this list:
316
"Key has been compromised"
317
Use this if you have a reason to believe that unauthorized persons
318
got access to your secret key.
320
Use this if you have replaced this key with a newer one.
321
"Key is no longer used"
322
Use this if you have retired this key.
323
"User ID is no longer valid"
324
Use this to state that the user ID should not longer be used;
325
this is normally used to mark an email address invalid.
328
.gpg.ask_revocation_reason.text
329
# revoke.c (ask_revocation_reason)
330
If you like, you can enter a text describing why you issue this
331
revocation certificate. Please keep this text concise.
332
An empty line ends the text.
338
.gpgsm.root-cert-not-trusted
339
# This text gets displayed by the audit log if
340
# a root certificates was not trusted.
341
The root certificate (the trust-anchor) is not trusted. Depending on
342
the configuration you may have been prompted to mark that root
343
certificate as trusted or you need to manually tell GnuPG to trust that
344
certificate. Trusted certificates are configured in the file
345
trustlist.txt in GnuPG's home directory. If you are in doubt, ask
346
your system administrator whether you should trust this certificate.
353
# mode: default-generic
added
removed
doc/help.txt
