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