1 |
twoaday |
222 |
\input texinfo |
2 |
|
|
|
3 |
|
|
@setfilename WinPT |
4 |
|
|
|
5 |
|
|
This file describes the Windows Privacy Tray program and its main functions |
6 |
|
|
|
7 |
|
|
This file is free under the terms of the GNU General Public License v2. |
8 |
|
|
|
9 |
|
|
Copyright (C) 2006 Timo Schulz |
10 |
|
|
|
11 |
twoaday |
232 |
Version 0.2.0 |
12 |
twoaday |
222 |
|
13 |
|
|
@settitle WinPT - The Windows Privacy Tray; a free GPG front-end for Windows |
14 |
|
|
|
15 |
|
|
@section Requirements for WinPT |
16 |
|
|
|
17 |
|
|
First you need to have a working GnuPG 1.4 installtion on the machine you |
18 |
|
|
plan to install WinPT. If you don't have GPG in your machine, please |
19 |
|
|
visit http://www.gnupg.org and download the latest GPG version there. |
20 |
|
|
It comes with a graphical installer so there is no need to do this |
21 |
|
|
step manually. |
22 |
|
|
|
23 |
|
|
You need at least Windows 98/2K/XP, but Windows XP or better is |
24 |
|
|
recommend. The program also works on NT/95/ME but there is no support |
25 |
twoaday |
246 |
for these OS versions any longer. Mainly because the OS vendor also |
26 |
|
|
dropped support and no bug fixes will be provided any longer. |
27 |
twoaday |
222 |
|
28 |
twoaday |
224 |
@section A short Introduction |
29 |
twoaday |
225 |
|
30 |
twoaday |
224 |
WinPT is a graphical GnuPG front-end which resides in the task bar. |
31 |
|
|
It is divided into several, so-called, managers. There is a manager |
32 |
|
|
for the keyring, for files and for smart cards. The aim of the program |
33 |
twoaday |
246 |
is to secure email communication and to perform file encryption and |
34 |
|
|
to allow an easy and user friendly way for key management. |
35 |
twoaday |
222 |
|
36 |
twoaday |
224 |
@subsection What is GnuPG |
37 |
|
|
GnuPG is a tool for secure communication and data storage. |
38 |
|
|
It can be used to encrypt data and to create digital signatures. |
39 |
|
|
It includes an advanced key management facility and is compliant |
40 |
|
|
with the proposed Internet standard as described in RFC2440. |
41 |
|
|
|
42 |
|
|
@subsection The Web of Trust |
43 |
|
|
For a detailled description of these and other GnuPG topics, I |
44 |
|
|
recommend the available literature at http://www.gnupg.org. But |
45 |
|
|
at least a general overview should be given here. |
46 |
|
|
|
47 |
|
|
The certification scheme of OpenPGP does not base on a hirachical |
48 |
|
|
approach. Instead it uses a combination of ownertrust and direct |
49 |
|
|
key certification. Here is an example with Alice, Bob, Carol and Dave. |
50 |
|
|
|
51 |
|
|
Alice knows Bob and checked the fingerprint of Bob's key when he |
52 |
|
|
met him personally. Thus she knows that the key really belongs to |
53 |
|
|
its owner and he trusts Bob to certify other keys. Then she issued |
54 |
|
|
a signature on Bob's key. Bob knows Carol and also checked her identity. |
55 |
|
|
Then he signed her key. Alice does not know Carol, but he knows Bob |
56 |
|
|
and Bob trusts Carol. And because Alice trusts Bob, at a level she |
57 |
|
|
decided before, he also trusts Carol. It's a transitiv relation. |
58 |
|
|
Dave is isolated and does not know anybody from the mentioned persons, |
59 |
|
|
thus he is not in the WoT. |
60 |
|
|
Another very important point is, that the signer can decide, |
61 |
|
|
after the certification, how much he trusts the key owner to |
62 |
|
|
certify other keys. |
63 |
|
|
|
64 |
|
|
It is very important to check the identify of a key owner. Mostly |
65 |
|
|
this is done by comparing the fingerprint, which were submitted |
66 |
|
|
by phone or written down at a personal meeting, with the fingerprint |
67 |
|
|
of the key in the keyring. Please bear in mind that anybody can create |
68 |
|
|
a key with an email address and a specific name. Thus it is not |
69 |
|
|
recommend to sign keys without doing this check before! |
70 |
|
|
|
71 |
|
|
The fingerprint of the key is hexadecial (160-bit) sequence divided |
72 |
|
|
into 10 groups of 4 hex digits. You can get the fingerprint of a key |
73 |
|
|
by opening the key property dialog. There you can mark the fingerprint |
74 |
twoaday |
231 |
and copy it to the clipboard. The fingerprint of a key can be compared |
75 |
|
|
to human fingerprints, it is unique for each key. |
76 |
twoaday |
224 |
|
77 |
|
|
Example: 1D75 8108 5BC9 D9FB E78B 2078 ED46 81C9 BF3D F9B4 |
78 |
|
|
|
79 |
twoaday |
227 |
It is a good idea to publish your fingerprint wherever possible. |
80 |
|
|
For example via a business card or your website. |
81 |
|
|
|
82 |
twoaday |
222 |
@section Installation of the Program |
83 |
|
|
|
84 |
|
|
It is always recommend to use the latest version of the program. You |
85 |
|
|
can download it from http://wald.intevation.org/projects/winpt. |
86 |
|
|
Download the zip file with the binaries inside and unpack them in |
87 |
|
|
a folder. All files need to be in the same folder, so if you change |
88 |
twoaday |
246 |
the folder do not forget to move all files. |
89 |
twoaday |
224 |
You should also download and verify the signature of the packet to |
90 |
|
|
make sure that the release is really authentic. |
91 |
twoaday |
222 |
|
92 |
|
|
To activate the program you just need to start WinPT.exe. You should |
93 |
|
|
now see a little (golden key) icon in the taskbar which indicates that |
94 |
|
|
the program is running. If you want to quit the program, right click |
95 |
|
|
on the symbol and select "Exit". |
96 |
|
|
|
97 |
|
|
Alternative, you may use one of the graphical GPG installers which |
98 |
|
|
are available on the internet. I recommend to use Gpg4Win which |
99 |
|
|
includes a set of very useful privacy tools, beside WinPT and it |
100 |
|
|
is very easy to use with an average size (~4MB). For non-German |
101 |
|
|
speaking users, I recommend the light version because it does not |
102 |
|
|
contain the 2 German PDF manuals. |
103 |
|
|
|
104 |
twoaday |
225 |
@subsection Getting the Source of the Program |
105 |
|
|
As free software, according to the GNU General Public License, |
106 |
|
|
WinPT also offers the source code for the program. It can be used |
107 |
|
|
for reviews, to compile your own binary and/or to modify and/or |
108 |
|
|
redistribute it or just to learn how it works. The source is available |
109 |
|
|
at the same place you downloaded the binary. If not, you should |
110 |
|
|
contact the author of the site. |
111 |
|
|
The entire program can be build with free software; the default |
112 |
|
|
environment is a cross-compiler hosted on a Linux box. All you |
113 |
|
|
need is the mingw32 packages, a working autoconf environment |
114 |
|
|
and the libs WinPT depends on (currently gpgme and libgpg-error). |
115 |
|
|
It is also possible to build the binary with cygwin/mingw32 on |
116 |
|
|
Windows but this environment is not actively supported and propably |
117 |
|
|
needs adjustment of the source. |
118 |
|
|
|
119 |
twoaday |
222 |
@subsection Configure the Program |
120 |
|
|
After the installation not much of the default settings need to |
121 |
|
|
be changed. If you prefer a special keyserver, it is propably a good |
122 |
|
|
idea to open the keyserver dialog and to set one of the existing |
123 |
|
|
keyservers as the default or create a new entry and mark it as the |
124 |
|
|
new default. The default keyserver is subkeys.pgp.net, which is |
125 |
|
|
the best choice for most users. |
126 |
|
|
|
127 |
|
|
@subsection GPG Options |
128 |
|
|
For expert users, the GPG preference dialog might contain some |
129 |
|
|
interesting options. For example to set the expiration date of |
130 |
|
|
a signature and/or to set the signing level for key signing. |
131 |
|
|
It also allows to set a default 'encrypt-to' key and to set |
132 |
|
|
the comment in ASCII armored files. |
133 |
|
|
|
134 |
|
|
@subsection Preferences |
135 |
|
|
In the WinPT preference dialog, the user can modify and/or disable |
136 |
|
|
the default options. For new users it is suggested to leave the |
137 |
|
|
default values as they are, except when there are problems related |
138 |
|
|
to the hotkeys. |
139 |
|
|
|
140 |
|
|
To enable keyring backups, the user can either decide to use the |
141 |
|
|
GPG home directory as the backup folder or any other folder. In |
142 |
twoaday |
224 |
the latter case, a folder needs to be chosen. |
143 |
twoaday |
222 |
|
144 |
|
|
|
145 |
|
|
@section The First Start |
146 |
twoaday |
225 |
|
147 |
twoaday |
222 |
This section is only important for people who never installed |
148 |
twoaday |
246 |
and/or used WinPT before and thus no keyrings are available. |
149 |
twoaday |
222 |
|
150 |
|
|
When the program is started the first time, it offers two choices. |
151 |
|
|
The one is to generate a key pair and the other is to copy |
152 |
|
|
existing GPG keyrings into the current installation. |
153 |
|
|
|
154 |
|
|
We assume the user will select the first entry. |
155 |
|
|
|
156 |
|
|
Now a new dialog is shown which requests some information from |
157 |
|
|
the user to allow a meaningful association between the key and |
158 |
twoaday |
246 |
the user. If the user prefer RSA keys, the check box should be marked. |
159 |
|
|
But this is a decision of personal taste and does not influence the security |
160 |
|
|
or anything else. |
161 |
twoaday |
222 |
If the entered data is OK, WinPT then generates a new key pair. As long |
162 |
|
|
as this step takes, a progress dialog is shown to indicate the |
163 |
|
|
enduring process. When the generation of the keypair is done, WinPT |
164 |
|
|
offers the chance to backup the existing keyrings. This is definitely |
165 |
|
|
an important decision because if the keyring will get corrupted |
166 |
|
|
or lost, there is no way to recover the encrypted data. That is |
167 |
|
|
why it is also important to store the backup, at least of the |
168 |
|
|
secret keyring, at a @strong{safe} place. |
169 |
|
|
|
170 |
twoaday |
246 |
@section The Passphrase for the Secret Key |
171 |
|
|
First a short explaination what passphrase is. A passphrase is like |
172 |
|
|
a password but usually longer, maybe a sentence, which can consists of |
173 |
|
|
any 7-bit ASCII characters. It is used to protect your secret key |
174 |
|
|
and thus it is very import to chose a secure passphrase. If your |
175 |
|
|
computer, and thus the secret key, were stolen and an attacker can |
176 |
|
|
guess your passphrase he is able to decrypt all your data and to |
177 |
|
|
create signatures in your name! A good passphrase is difficult |
178 |
|
|
to guess but easy to remember and should be at least 10 characters long. |
179 |
|
|
An easy way to generate a strong passphrase is to use a sentence only |
180 |
|
|
you know but you can easily remind and then take the first letter of |
181 |
|
|
each word, plus some special characters and maybe even some intentionally |
182 |
|
|
made spelling mistakes. |
183 |
|
|
|
184 |
|
|
Example: Row - row - row your boat, gently down the stream |
185 |
|
|
Passphrase: R-r-ryb,gdt |
186 |
|
|
|
187 |
|
|
Never write down or passphrase or share it among other people! |
188 |
|
|
|
189 |
twoaday |
222 |
@section Keyserver Access |
190 |
twoaday |
225 |
|
191 |
twoaday |
222 |
An easy way to retrieve keys is the keyserver. You can think of |
192 |
|
|
it like a huge database with a lot of keys as its content. It is |
193 |
|
|
possible to search keys by a pattern, a keyid or even a fingerprint. |
194 |
|
|
WinPT allows to access different kind of keyservers. For example |
195 |
|
|
LDAP, HKP, Finger and HTTP. But the focus will be set on HKP because |
196 |
|
|
this is the common case. |
197 |
|
|
|
198 |
|
|
In some situations WinPT asks the user whether to retrieve keys |
199 |
|
|
automatically. One example is the signature verification when the |
200 |
|
|
key that issued the signature was not found in the keyring. |
201 |
|
|
|
202 |
|
|
The main keyserver dialog allows to fetch one or more keys directly |
203 |
|
|
or to search for a given pattern. |
204 |
|
|
|
205 |
|
|
@subsection Retrieve a key by Key ID |
206 |
twoaday |
224 |
The best way to fetch a key from the server is by the key ID. |
207 |
|
|
Just enter the key ID, it is always a good idea to prefix it |
208 |
|
|
with 0x and click the "Receive" button. |
209 |
twoaday |
222 |
|
210 |
twoaday |
224 |
An example: |
211 |
|
|
|
212 |
|
|
pattern: 0xBF3DF9B4 |
213 |
|
|
|
214 |
|
|
[Receive] |
215 |
|
|
|
216 |
|
|
|
217 |
twoaday |
222 |
@subsection Retrieve a key by its email address |
218 |
twoaday |
224 |
If you only know the email address from your partner, you can |
219 |
|
|
enter it instead of the key ID. It is unlikely but possible |
220 |
|
|
that there are more keys with the same address. In this situation, |
221 |
|
|
WinPT will warn you that multiple keys were imported. The difference |
222 |
|
|
to the search function is, that the keys were dirctly fetched and |
223 |
|
|
not displayed as a key result list. |
224 |
twoaday |
222 |
|
225 |
twoaday |
224 |
|
226 |
|
|
An example: |
227 |
|
|
|
228 |
|
|
pattern: name_of_friend@@gmx.net |
229 |
|
|
|
230 |
|
|
[Receive] |
231 |
|
|
|
232 |
|
|
|
233 |
twoaday |
222 |
@subsection Search for a key by pattern |
234 |
|
|
If you want to communicate with a new mail partner and you are |
235 |
|
|
not sure about the key ID, it can be useful to search for his |
236 |
|
|
email address. This address is considered as quite unique. |
237 |
|
|
|
238 |
|
|
An example: |
239 |
|
|
|
240 |
twoaday |
224 |
pattern: winpt@@windows-privacy-tray.com |
241 |
twoaday |
222 |
|
242 |
|
|
[Search] |
243 |
|
|
|
244 |
|
|
Now a dialog is opened with a list of all keys which matched |
245 |
|
|
the search string. If the name @strong{and} the email address |
246 |
|
|
is known, the matching key should be selected and "Receive" |
247 |
|
|
should be clicked. Then the key will be downloaded and added |
248 |
|
|
to your keyring. Now you can encrypt data with this key, for |
249 |
|
|
example an email. |
250 |
|
|
|
251 |
twoaday |
224 |
@subsection Sending a Key to the Keyserver |
252 |
|
|
After you generated a new key pair, it is a good idea to send your |
253 |
|
|
key to the keyserver to make it available for other users. If you |
254 |
|
|
issue a signature, the key ID is part of the signature and people can |
255 |
|
|
automatically retrieve your key when they try to verify the signature. |
256 |
twoaday |
222 |
|
257 |
twoaday |
224 |
Actually, the action is performed in the Key Manager and not in the |
258 |
|
|
keyserver dialog. Just open the Key Manager, select the key you want |
259 |
|
|
to send right-click on it and chose "Send to Keyserver" in the popup |
260 |
|
|
menu. Then a message box with the result is shown. |
261 |
|
|
|
262 |
|
|
@subsection Add, Delete or Edit a Keyserver Entry |
263 |
|
|
The keyserver dialog allow to change the existing keyserver entries, |
264 |
|
|
to delete them or to add new entries. Just right click on a selected |
265 |
|
|
item and a popup menu will be shown with ("Edit", "Remove" and "New"). |
266 |
|
|
|
267 |
|
|
@section Using the Clipboard |
268 |
twoaday |
225 |
|
269 |
twoaday |
224 |
A major aim from the first day was, that the program does not |
270 |
|
|
depend on a special mailer client. For this reason it uses the |
271 |
|
|
clipboard to encrypt and/or sign data. |
272 |
|
|
For the examples, let's assume that you want to write a new |
273 |
|
|
mail or that you received a mail protected by GnuPG. |
274 |
|
|
|
275 |
|
|
@subsection Encrypt Data in the Clipboard |
276 |
|
|
Just copy the text from the mailer window into the clipboard. |
277 |
|
|
This is usually done by CTRL+C, make sure you really selected |
278 |
|
|
all portions of the text. Then right-click on the tray icon |
279 |
|
|
and select Clipboard->Encryption. Now a dialog is shown to |
280 |
|
|
select the recipients. This means you need to select all |
281 |
|
|
keys which should be able to decrypt the mail. Confirm with "OK". |
282 |
|
|
GnuPG now encrypts the data with the selected recipients. At the |
283 |
|
|
end a message box with the result is shown. Now the clipboard should |
284 |
|
|
contain the encrypted data. Just paste it into the mailer window. |
285 |
|
|
The output should contain a header and a footer |
286 |
|
|
"BEGIN PGP MESSAGE" and "END PGP MESSAGE. |
287 |
|
|
|
288 |
|
|
@subsection Decrypt/Verify Data from the Clipboard |
289 |
twoaday |
232 |
The most common case is propably that you got a signed email and |
290 |
|
|
now you want to verify it. For this procedure, you have to copy |
291 |
|
|
the entire signature in the clipboard. The easiest way is to |
292 |
|
|
use CTRL+A and CTRL+C, then all available text will be copied. |
293 |
|
|
WinPT (GnuPG) is smart enough to figure out the signature related |
294 |
|
|
data. Now go to the taskbar, display the popup menu and select |
295 |
|
|
Clipboard->Decrypt/Verify. Now a new dialog, the verify dialog, |
296 |
|
|
should be available on screen with all information about the |
297 |
|
|
signature. For example who is the signer, when was it signed |
298 |
|
|
how much do you try this key and what was signed and most |
299 |
|
|
important, the status of it (is the signature good or BAD). |
300 |
|
|
A special case is when you don't have the public key to verify |
301 |
|
|
the signature, if this happens WinPT offers to download the key |
302 |
|
|
from the default keyserver. If the key was not found, the procedure |
303 |
|
|
is aborted because without the key the sig cannot bed checked. |
304 |
twoaday |
224 |
|
305 |
|
|
@subsection Sign the Clipboard |
306 |
twoaday |
232 |
We assume that text that shall be signed is already in the |
307 |
|
|
clipboard. If not, select the text you want to sign and copy |
308 |
|
|
with via CTRL+C in the clipboard. Now go to the taskbar and |
309 |
|
|
open the peopup menu, Clipboard->Sign. If you just have one |
310 |
|
|
secret key, the passphrase dialog will be automatically shown. |
311 |
|
|
All you need is to enter your passphrase and confirm. In case |
312 |
|
|
of more available secret keys, a list with all keys is shown |
313 |
|
|
and you can select which key shall be used for signing. |
314 |
|
|
The output is always a cleartext signature which is in text |
315 |
|
|
format. Do not try to sign binary clipboard data, the result |
316 |
|
|
would be unpredictable and not readable by human beings. |
317 |
twoaday |
224 |
|
318 |
twoaday |
232 |
@section The Current Window Support |
319 |
|
|
Compared to the clipboard mode, the CWS mode has some advantages. |
320 |
|
|
Let us assume that you want to extract text from an editor window. |
321 |
|
|
With the CWS mode, the program automatically tries to focus the |
322 |
|
|
window to select the text and to copy it to the clipboard and |
323 |
|
|
execute the selected command (Sign, Encrypt, Decrypt). |
324 |
|
|
No manual user interaction is needed. Except this different behaviour, |
325 |
|
|
it is very likewise to the clipboard mode and thus we do not describe |
326 |
|
|
each command again. |
327 |
|
|
|
328 |
twoaday |
224 |
@section The Key Manager |
329 |
twoaday |
225 |
|
330 |
twoaday |
224 |
This part of the program is propably most important for many users. |
331 |
|
|
It contains function to manage your keyring and to perform actions |
332 |
|
|
which are required and/or useful in the OpenPGP environment. |
333 |
|
|
|
334 |
|
|
@subsection Tips |
335 |
|
|
|
336 |
|
|
@itemize @bullet |
337 |
|
|
|
338 |
|
|
@item |
339 |
|
|
If you want to import quickly a key from a into the keyring, just |
340 |
|
|
drag and drop the file into the Key Manager window. Then the import |
341 |
|
|
procedure will be automatically started. |
342 |
|
|
|
343 |
|
|
@item |
344 |
|
|
Key which were fetched from keyservers often contain a lot of, |
345 |
|
|
maybe obsolete, self signatures, if you want to get rid of them |
346 |
|
|
you can use the Key Edit->Clean feature. Just start the edit |
347 |
|
|
dialog and select the clean command. That's it. |
348 |
|
|
|
349 |
|
|
@item |
350 |
|
|
The keyserver dialog does not allow to import a key directly |
351 |
|
|
via an URL, as an alternative you may use the "Import HTTP..." |
352 |
|
|
feature in the Key Manager. With it you can directly fetch keys |
353 |
|
|
from the web (Example: http://www.users.my-isp.de/~joe/gpg-keys.asc). |
354 |
|
|
|
355 |
|
|
@item |
356 |
|
|
To customize the parameters of the generated key, you can use |
357 |
|
|
the expert key generation. It allows you to set the public key |
358 |
|
|
algorithm and/or the size of the key directly. |
359 |
|
|
|
360 |
twoaday |
225 |
@item |
361 |
|
|
Most of the list view based dialogs allow to use the right |
362 |
|
|
mouse button, to show popup menus with available commands. |
363 |
|
|
|
364 |
twoaday |
224 |
@end itemize |
365 |
|
|
|
366 |
twoaday |
225 |
@subsection Create a Revocation Certificate |
367 |
|
|
|
368 |
|
|
It is very important to do this step early as possible. With this |
369 |
|
|
certificate, you can revoke your entire key. The reason for this |
370 |
|
|
can be for example, that your key is no longer used or even compromised. |
371 |
|
|
After you generated the revoc cert, you should move it to a secure place |
372 |
|
|
because anybody who gets access to it, can render your key unuseable. |
373 |
|
|
|
374 |
|
|
Just right-click on your key and select "Revoke Cert". If you do this |
375 |
|
|
step directly after key generation, there is no need to change the |
376 |
|
|
default values. Just select a file name and enter the passphrase. |
377 |
|
|
The program issues a warning which should be read carefully. |
378 |
|
|
|
379 |
twoaday |
227 |
@subsection Adding a new Secondary Key |
380 |
twoaday |
222 |
|
381 |
|
|
For most users the existing keys in the key pair are enough |
382 |
|
|
and no extra key is needed. But there are some exceptions. |
383 |
|
|
|
384 |
|
|
@itemize @bullet |
385 |
|
|
|
386 |
|
|
@item |
387 |
|
|
The primary key has no secondary key and the primary key is not |
388 |
|
|
able to encrypt data. In this case it can be a good idea to |
389 |
|
|
add a secondary encryption key. |
390 |
|
|
|
391 |
|
|
@item |
392 |
|
|
A lot of people use secondary encryption keys with an expiration |
393 |
|
|
date. Usually the key is valid for 1-2 years. After the key is expired, |
394 |
|
|
a new key is needed in order to encrypt data. |
395 |
|
|
|
396 |
|
|
@end itemize |
397 |
|
|
|
398 |
|
|
What kind of public key algorithm should be selected is a matter |
399 |
|
|
of taste. RSA and ElGamal are both capable for encryption. For most |
400 |
|
|
users it's a good idea to let the program chose the key size (in bits). |
401 |
|
|
The default settings should be secure enough for most purposes. |
402 |
|
|
|
403 |
twoaday |
227 |
@subsection Adding a new User ID |
404 |
twoaday |
222 |
If you got a new email account, it's propably a good idea to |
405 |
|
|
add these new account to your key also. For example: |
406 |
|
|
|
407 |
|
|
A new account was registed at gmail.com (john.doo@@gmail.com). |
408 |
|
|
Then you should create a new user ID with the following fields: |
409 |
|
|
|
410 |
|
|
name: John Doo |
411 |
|
|
|
412 |
|
|
email: john.doo@@gmail.com |
413 |
|
|
|
414 |
|
|
comment: (optional) |
415 |
|
|
|
416 |
|
|
Now email programs are able to associate this address with your |
417 |
|
|
key when somebody wants to send you a protected mail to this account. |
418 |
|
|
|
419 |
twoaday |
227 |
@subsection Adding a new Photographic ID |
420 |
twoaday |
222 |
With this function you can add a photo to your public. It will be |
421 |
|
|
displayed in the key property dialog. |
422 |
|
|
|
423 |
|
|
You just need to select a JPEG file which contains the photo and |
424 |
|
|
enter your passphrase and confirm with OK. Please read the note |
425 |
|
|
in the dialog carefully to make sure the photo has a proper size |
426 |
|
|
(file, height and weight). |
427 |
|
|
|
428 |
twoaday |
227 |
@subsection Adding a new Designated Revoker |
429 |
twoaday |
222 |
If you want to allow another key to revoke your own key, this |
430 |
|
|
might be useful if you lost your secret or a simliar situation, |
431 |
|
|
you can use this function to add a designated revoker to your key. |
432 |
|
|
|
433 |
|
|
All you need to do is to select the key you want to add as a desig |
434 |
|
|
revoker. But please bear in mind that this procedure cannot be undone |
435 |
|
|
and that this person really has the power to make your public key |
436 |
|
|
unuseable. You really should trust the selected key, in case it is |
437 |
|
|
not a key owned by yourself. |
438 |
|
|
|
439 |
twoaday |
226 |
@subsection Export a Public Key |
440 |
|
|
There are several reason why to export a public key and there |
441 |
|
|
are also several ways to do it. If you want to send the key |
442 |
|
|
directly to a mail recipient, you can select the key, right-click, |
443 |
|
|
and select "Send Key to Mail Recipient". As an alternative, you |
444 |
|
|
can also export it to the clipboard or to a file. To export a |
445 |
|
|
key to the clipboard, you can select "Copy key to Clipboard" |
446 |
|
|
in the popup menu of the selected key. To export it to a file, |
447 |
|
|
you need to select the menu "Key" and then "Export...". The |
448 |
|
|
program will automatically suggest a name for the output. |
449 |
|
|
|
450 |
|
|
@subsection Import a Public Key |
451 |
|
|
Similar to the key import, the import of a key can be done in |
452 |
|
|
several ways. First, let's assume you got a mail with an OpenPGP |
453 |
|
|
key included as inline text. Then you can use the current window |
454 |
|
|
feature and "Decrypt/Verify" to import the key. Alternative you |
455 |
|
|
also may use the clipboard. To achieve this, you first need to |
456 |
|
|
select the entire key (CTRL+A) and then copy it to the clipboard |
457 |
|
|
(CTRL+C), then use the Key Manager (Edit->Paste) to import it. |
458 |
|
|
If the key is stored as an attachment, or you want to import |
459 |
|
|
a key from a file in general, just drag the file and drop it |
460 |
|
|
into the Key Manager window or use "Key" -> "Import...". |
461 |
|
|
|
462 |
twoaday |
227 |
@subsection Sign a Public Key |
463 |
|
|
If you verified that a key really belongs to its owner, you |
464 |
|
|
should sign the key to integrate it into your Web of Trust |
465 |
|
|
and also to mark the key as valid in your keyring. Do not sign |
466 |
|
|
a key you just got via email with the request to sign it. Anybody |
467 |
|
|
can create a key with your (or better ANY) name, these information |
468 |
|
|
are no hint to whom the key really belongs. You can check a key |
469 |
|
|
by meeting or calling the key owner and verify the key fingerprint |
470 |
|
|
of the key with the one published by the key owner. Additional checks |
471 |
|
|
should be to watch at his driver license or the identity card to make |
472 |
|
|
sure that name of the key matches the name of the key owner. After |
473 |
|
|
this procedure is done, you can open the Key Manager, select the |
474 |
|
|
right key and either use the context menu "Sign Key" or use the |
475 |
|
|
toolbar button. |
476 |
|
|
|
477 |
|
|
The next dialog will summarize the key information and some |
478 |
|
|
additional options. For example if the signature should be |
479 |
|
|
local or exportable. Local means the signature will be stripped |
480 |
|
|
if you export the key and no one else except you can use it to |
481 |
|
|
calculate the validity. If you mark the signature exportable, |
482 |
|
|
any other user can see and use it. Now you can select the key |
483 |
|
|
you want to use to sign and enter the passphrase. Confirm with "OK" |
484 |
|
|
and the key will be signed. Now the validity of the new key is |
485 |
|
|
"Full". It is propably a good idea to set the ownertrust of the |
486 |
|
|
key. For a detailled description, see the chapter "Key Ownertrust". |
487 |
|
|
|
488 |
|
|
@subsection Key Ownertrust |
489 |
|
|
First we should explain what the ownertrust of a key is. The ownertrust |
490 |
|
|
is a measurement how much you trust somebody to certify and check keys |
491 |
|
|
of other people. For example, if you know that Bob is really the owner |
492 |
|
|
of the key, you should sign it. But he is also known to sign other keys |
493 |
|
|
without checking the idenity of the other key owner. Values for the |
494 |
|
|
ownertrust are 1) Don't Know 2) Don't Trust 3) Marginal 4) Full |
495 |
|
|
and thus you should propably use an ownertrust value like "Marginal". |
496 |
|
|
But this is a personal decision and stored in a separate file and |
497 |
|
|
never exported with the public keys. For further information, please |
498 |
|
|
take a look into the GNU Privacy Handbook. |
499 |
|
|
Just a last work on Key Pairs, they are automatically marked as |
500 |
|
|
"Ultimate" because the key belongs to you and you trust it implicit. |
501 |
twoaday |
242 |
|
502 |
|
|
@section The File Manager |
503 |
|
|
|
504 |
|
|
@subsection Introduction |
505 |
|
|
The File Manager is no replacement for an Explorer Extension. |
506 |
|
|
If you secure your files frequently and you want to do this |
507 |
|
|
fast and easy, I suggest to install GPGee. It is a program |
508 |
|
|
which integrates itself into the explorer and provide menu |
509 |
|
|
entries in the context menu of files and directory. But the |
510 |
|
|
File Manager can be very useful if you just want to decrypt |
511 |
|
|
and/or encrypt some files without additional programs. You |
512 |
|
|
can find the File Manager via the symbol in the taskbar, |
513 |
|
|
right click and then "File Manager". |
514 |
|
|
|
515 |
|
|
@subsection An Overview of the GUI |
516 |
|
|
First there are different ways to add (open) files in the |
517 |
|
|
Key Manager. The easiest way is to use drag and drop to |
518 |
|
|
add files into the File Manager. Just drag a file from the |
519 |
|
|
explorer and drop it into the File Manager window. The second |
520 |
|
|
way is to use File->Open. A dialog opens which is common for |
521 |
|
|
all "File Open" operations in most Windows application. Now |
522 |
|
|
you can select one or more files and confirm. The files will |
523 |
|
|
be automatically added to the File Manager window. The main |
524 |
|
|
window consists of a listview with three rows. |
525 |
|
|
|
526 |
|
|
The first row is the status of the file. It can be "ENCRYPTED", |
527 |
|
|
"SIGNED", "PUBKEY", "SECKEY", "SIG" or "UNKNOWN". Dependent on |
528 |
|
|
the file status, the File Manager offers different choices. For example |
529 |
|
|
"SIG" enables the verify options in the (popup) menu. "UNKNOWN" is |
530 |
|
|
the default for all plaintext files. |
531 |
|
|
The second row is the file name. And the last row is the status of |
532 |
|
|
the operation. It can be either "", "SUCCESS" or "FAILED". An empty status |
533 |
|
|
means no operation was started yet. FAILED indicates that the |
534 |
|
|
GnuPG operation failed. In this case an error message was issued before. |
535 |
|
|
|
536 |
|
|
Now it follows an example: |
537 |
|
|
We assume that user wants to encrypt "c:\My Ideas\GPG GUI.txt". |
538 |
|
|
Drag the file from the Explorer and drop it into the open File |
539 |
|
|
Manager, the main window. The file will be added and recognized |
540 |
|
|
as "UNKNOWN". Now we select the file and right click, a popup |
541 |
|
|
menu is shown and we select "Encrypt". An new dialog is opened |
542 |
|
|
which looks similar to the Clipboard Encryption dialog. Just |
543 |
|
|
select the recipients and confirm. In contrast to clipboard encryption, |
544 |
|
|
file encryption offers some more extra options. They are described |
545 |
|
|
later. And hour glass will be shown as long as GnuPG takes to encrypt |
546 |
|
|
the file. When the procedure is done, the third row should be change |
547 |
|
|
to "SUCCESS" and the first row to "ENCRYPTED". |
548 |
|
|
|
549 |
|
|
@subsection General Options |
550 |
|
|
Now we describe the general options which are possible in some |
551 |
|
|
File Manager dialogs. |
552 |
|
|
|
553 |
|
|
@itemize |
554 |
|
|
|
555 |
|
|
@item Text Output |
556 |
|
|
When this option is checked, the output will be encoded in ASCII armor. |
557 |
|
|
This can be useful if the file should be transfered via email. The |
558 |
|
|
size of the output file is larger than the usual binary output. |
559 |
|
|
|
560 |
|
|
@item Wipe Original |
561 |
|
|
If this option is checked, the original file will be deleted after |
562 |
|
|
successfull encryption. This can be useful if data should not be |
563 |
|
|
available in plaintext any longer on a machine. |
564 |
|
|
|
565 |
|
|
@end itemize |
566 |
|
|
|
567 |
twoaday |
222 |
@bye |