1
# help..txt - 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
.#gpg.edit_ownertrust.value
21
# fixme: Please translate and remove the hash mark from the key line.
22
It's up to you to assign a value here; this value will never be exported
23
to any 3rd party. We need it to implement the web-of-trust; it has nothing
24
to do with the (implicitly created) web-of-certificates.
27
.#gpg.edit_ownertrust.set_ultimate.okay
28
# fixme: Please translate and remove the hash mark from the key line.
29
To build the Web-of-Trust, GnuPG needs to know which keys are
30
ultimately trusted - those are usually the keys for which you have
31
access to the secret key. Answer "yes" to set this key to
36
.#gpg.untrusted_key.override
37
# fixme: Please translate and remove the hash mark from the key line.
38
If you want to use this untrusted key anyway, answer "yes".
41
.#gpg.pklist.user_id.enter
42
# fixme: Please translate and remove the hash mark from the key line.
43
Enter the user ID of the addressee to whom you want to send the message.
47
# fixme: Please translate and remove the hash mark from the key line.
48
Select the algorithm to use.
50
DSA (aka DSS) is the Digital Signature Algorithm and can only be used
53
Elgamal is an encrypt-only algorithm.
55
RSA may be used for signatures or encryption.
57
The first (primary) key must always be a key which is capable of signing.
60
.#gpg.keygen.algo.rsa_se
61
# fixme: Please translate and remove the hash mark from the key line.
62
In general it is not a good idea to use the same key for signing and
63
encryption. This algorithm should only be used in certain domains.
64
Please consult your security expert first.
68
# fixme: Please translate and remove the hash mark from the key line.
69
Enter the size of the key
72
.#gpg.keygen.size.huge.okay
73
# fixme: Please translate and remove the hash mark from the key line.
77
.#gpg.keygen.size.large.okay
78
# fixme: Please translate and remove the hash mark from the key line.
83
# fixme: Please translate and remove the hash mark from the key line.
84
Enter the required value as shown in the prompt.
85
It is possible to enter a ISO date (YYYY-MM-DD) but you won't
86
get a good error response - instead the system tries to interpret
87
the given value as an interval.
90
.#gpg.keygen.valid.okay
91
# fixme: Please translate and remove the hash mark from the key line.
96
# fixme: Please translate and remove the hash mark from the key line.
97
Enter the name of the key holder
101
# fixme: Please translate and remove the hash mark from the key line.
102
please enter an optional but highly suggested email address
106
# fixme: Please translate and remove the hash mark from the key line.
107
Please enter an optional comment
110
.#gpg.keygen.userid.cmd
111
# fixme: Please translate and remove the hash mark from the key line.
112
N to change the name.
113
C to change the comment.
114
E to change the email address.
115
O to continue with key generation.
116
Q to to quit the key generation.
119
.#gpg.keygen.sub.okay
120
# fixme: Please translate and remove the hash mark from the key line.
121
Answer "yes" (or just "y") if it is okay to generate the sub key.
125
# fixme: Please translate and remove the hash mark from the key line.
130
# fixme: Please translate and remove the hash mark from the key line.
131
When you sign a user ID on a key, you should first verify that the key
132
belongs to the person named in the user ID. It is useful for others to
133
know how carefully you verified this.
135
"0" means you make no particular claim as to how carefully you verified the
138
"1" means you believe the key is owned by the person who claims to own it
139
but you could not, or did not verify the key at all. This is useful for
140
a "persona" verification, where you sign the key of a pseudonymous user.
142
"2" means you did casual verification of the key. For example, this could
143
mean that you verified the key fingerprint and checked the user ID on the
144
key against a photo ID.
146
"3" means you did extensive verification of the key. For example, this could
147
mean that you verified the key fingerprint with the owner of the key in
148
person, and that you checked, by means of a hard to forge document with a
149
photo ID (such as a passport) that the name of the key owner matches the
150
name in the user ID on the key, and finally that you verified (by exchange
151
of email) that the email address on the key belongs to the key owner.
153
Note that the examples given above for levels 2 and 3 are *only* examples.
154
In the end, it is up to you to decide just what "casual" and "extensive"
155
mean to you when you sign other keys.
157
If you don't know what the right answer is, answer "0".
160
.#gpg.change_passwd.empty.okay
161
# fixme: Please translate and remove the hash mark from the key line.
165
.#gpg.keyedit.save.okay
166
# fixme: Please translate and remove the hash mark from the key line.
170
.#gpg.keyedit.cancel.okay
171
# fixme: Please translate and remove the hash mark from the key line.
175
.#gpg.keyedit.sign_all.okay
176
# fixme: Please translate and remove the hash mark from the key line.
177
Answer "yes" if you want to sign ALL the user IDs
180
.#gpg.keyedit.remove.uid.okay
181
# fixme: Please translate and remove the hash mark from the key line.
182
Answer "yes" if you really want to delete this user ID.
183
All certificates are then also lost!
186
.#gpg.keyedit.remove.subkey.okay
187
# fixme: Please translate and remove the hash mark from the key line.
188
Answer "yes" if it is okay to delete the subkey
191
.#gpg.keyedit.delsig.valid
192
# fixme: Please translate and remove the hash mark from the key line.
193
This is a valid signature on the key; you normally don't want
194
to delete this signature because it may be important to establish a
195
trust connection to the key or another key certified by this key.
198
.#gpg.keyedit.delsig.unknown
199
# fixme: Please translate and remove the hash mark from the key line.
200
This signature can't be checked because you don't have the
201
corresponding key. You should postpone its deletion until you
202
know which key was used because this signing key might establish
203
a trust connection through another already certified key.
206
.#gpg.keyedit.delsig.invalid
207
# fixme: Please translate and remove the hash mark from the key line.
208
The signature is not valid. It does make sense to remove it from
212
.#gpg.keyedit.delsig.selfsig
213
# fixme: Please translate and remove the hash mark from the key line.
214
This is a signature which binds the user ID to the key. It is
215
usually not a good idea to remove such a signature. Actually
216
GnuPG might not be able to use this key anymore. So do this
217
only if this self-signature is for some reason not valid and
218
a second one is available.
221
.#gpg.keyedit.updpref.okay
222
# fixme: Please translate and remove the hash mark from the key line.
223
Change the preferences of all user IDs (or just of the selected ones)
224
to the current list of preferences. The timestamp of all affected
225
self-signatures will be advanced by one second.
229
.#gpg.passphrase.enter
230
# fixme: Please translate and remove the hash mark from the key line.
231
Please enter the passhrase; this is a secret sentence
235
.#gpg.passphrase.repeat
236
# fixme: Please translate and remove the hash mark from the key line.
237
Please repeat the last passphrase, so you are sure what you typed in.
240
.#gpg.detached_signature.filename
241
# fixme: Please translate and remove the hash mark from the key line.
242
Give the name of the file to which the signature applies
245
.#gpg.openfile.overwrite.okay
246
# fixme: Please translate and remove the hash mark from the key line.
247
Answer "yes" if it is okay to overwrite the file
250
.#gpg.openfile.askoutname
251
# fixme: Please translate and remove the hash mark from the key line.
252
Please enter a new filename. If you just hit RETURN the default
253
file (which is shown in brackets) will be used.
256
.#gpg.ask_revocation_reason.code
257
# fixme: Please translate and remove the hash mark from the key line.
258
You should specify a reason for the certification. Depending on the
259
context you have the ability to choose from this list:
260
"Key has been compromised"
261
Use this if you have a reason to believe that unauthorized persons
262
got access to your secret key.
264
Use this if you have replaced this key with a newer one.
265
"Key is no longer used"
266
Use this if you have retired this key.
267
"User ID is no longer valid"
268
Use this to state that the user ID should not longer be used;
269
this is normally used to mark an email address invalid.
273
.#gpg.ask_revocation_reason.text
274
# fixme: Please translate and remove the hash mark from the key line.
275
If you like, you can enter a text describing why you issue this
276
revocation certificate. Please keep this text concise.
277
An empty line ends the text.
added
removed
doc/help.et.txt
