1 |
\input texinfo |
\input texinfo |
2 |
|
|
3 |
|
@c %**start of header |
4 |
@setfilename WinPT |
@setfilename WinPT |
5 |
|
@settitle WinPT - The Windows Privacy Tray; a free GPG front-end |
6 |
|
@afourpaper |
7 |
|
@c %**end of header |
8 |
|
|
9 |
This file describes the Windows Privacy Tray program and its main functions |
@titlepage |
10 |
|
@title Windows Privacy Tray |
11 |
|
|
12 |
This file is free under the terms of the GNU General Public License v2. |
@subtitle A free GUI Front-End for GNU Privacy Guard |
13 |
|
|
14 |
Copyright (C) 2006 Timo Schulz |
@author Timo Schlz, Sundar Pillay |
15 |
|
This file describes the Windows Privacy Tray program and its main functions |
16 |
|
This file is free under the terms of the GNU General Public License v2. |
17 |
|
Version 1.1.1 Copyright (C) 2006 Timo Schulz, Sundar Pillay |
18 |
|
@end titlepage |
19 |
|
|
|
Version 1.1.0 |
|
|
|
|
|
@settitle WinPT - The Windows Privacy Tray; a free GPG front-end |
|
20 |
|
|
21 |
@section Requirements for WinPT |
@section Requirements for WinPT |
22 |
|
|
326 |
No manual user interaction is needed. Except this different behaviour, it is very likewise to the |
No manual user interaction is needed. Except this different behaviour, it is very likewise to the |
327 |
clipboard mode and thus we do not describe each command again. |
clipboard mode and thus we do not describe each command again. |
328 |
|
|
329 |
|
But due to the nature of this mode, it is possible that some kind of windows are not supported. |
330 |
|
Which means that the program cannot extract the text from the window. There is nothing we can do |
331 |
|
about it, because it depends on the application itself how it reacts on certain Window messages. |
332 |
|
But all windows which support the default copy/paste/select all commands should make no problems. |
333 |
|
|
334 |
@section The Key Manager |
@section The Key Manager |
335 |
|
|
336 |
This part of the program is propably most important for many users. It contains function to |
This part of the program is propably most important for many users. It contains function to |
341 |
@itemize @bullet |
@itemize @bullet |
342 |
|
|
343 |
@item |
@item |
344 |
|
If you want to start the Key Manager directly, you can create a batch |
345 |
|
file with "winpt.exe --keymanager". This way you do not have to go to |
346 |
|
the task bar enable the icon and click on the Key Manager entry in the menu. |
347 |
|
|
348 |
|
@item |
349 |
If you want to import quickly a key from a into the keyring, just drag and drop the file into the |
If you want to import quickly a key from a into the keyring, just drag and drop the file into the |
350 |
Key Manager window. Then the import procedure will be automatically started. |
Key Manager window. Then the import procedure will be automatically started. |
351 |
|
|
578 |
GnuPG takes to encrypt the file. When the procedure is done, the third row should be change |
GnuPG takes to encrypt the file. When the procedure is done, the third row should be change |
579 |
to "SUCCESS" and the first row to "ENCRYPTED". |
to "SUCCESS" and the first row to "ENCRYPTED". |
580 |
|
|
581 |
|
@subsection Verify Detached Signatures |
582 |
|
Most of the signature are detached, which means that the signature is separated from the data. |
583 |
|
Usually you need to verify a detached signature when you have downloaded a software package or |
584 |
|
an update of it. The steps to verify such a signature are easy. Just open the File Manager and |
585 |
|
drag the detached signature in the File Manager window. |
586 |
|
Now select the signature and select "Verify" either via the popup menu or the File menu. |
587 |
|
In most cases you propably need to download the verification key, before you can verify the signature. |
588 |
|
|
589 |
@subsection General Options |
@subsection General Options |
590 |
Now we describe the general options which are possible in some File Manager dialogs. |
Now we describe the general options which are possible in some File Manager dialogs. |
591 |
|
|
712 |
existing documentation or write new docs. You could translate WinPT into a new language or |
existing documentation or write new docs. You could translate WinPT into a new language or |
713 |
maintain an existing language file. Of course it is also possible to contribute code or to |
maintain an existing language file. Of course it is also possible to contribute code or to |
714 |
become part of the WinPT developer crew. |
become part of the WinPT developer crew. |
|
Commercial support for WinPT is available via g10 Code GmbH. |
|
715 |
|
|
716 |
@subsection What I need for Development |
@subsection What I need for Development |
717 |
First, you need a Windows C-compiler and knowledge how to use the tools and the Win32 API. There |
First, you need a Windows C-compiler and knowledge how to use the tools and the Win32 API. There |