[Winpt-commits] r227 - in trunk: . Doc PTD Src
scm-commit@wald.intevation.org
scm-commit at wald.intevation.org
Wed Jun 14 08:57:59 CEST 2006
Author: twoaday
Date: 2006-06-14 08:57:57 +0200 (Wed, 14 Jun 2006)
New Revision: 227
Modified:
trunk/Doc/winpt.texi
trunk/PTD/resource.rc
trunk/Src/WinPT-en.rc
trunk/TODO
trunk/configure.ac
Log:
Modified: trunk/Doc/winpt.texi
===================================================================
--- trunk/Doc/winpt.texi 2006-06-12 13:40:21 UTC (rev 226)
+++ trunk/Doc/winpt.texi 2006-06-14 06:57:57 UTC (rev 227)
@@ -8,7 +8,7 @@
Copyright (C) 2006 Timo Schulz
-Version 0.0.0
+Version 0.1.0
@settitle WinPT - The Windows Privacy Tray; a free GPG front-end for Windows
@@ -73,6 +73,9 @@
Example: 1D75 8108 5BC9 D9FB E78B 2078 ED46 81C9 BF3D F9B4
+It is a good idea to publish your fingerprint wherever possible.
+For example via a business card or your website.
+
@section Installation of the Program
It is always recommend to use the latest version of the program. You
@@ -313,7 +316,7 @@
default values. Just select a file name and enter the passphrase.
The program issues a warning which should be read carefully.
- at subsection Adding a new secondary key
+ at subsection Adding a new Secondary Key
For most users the existing keys in the key pair are enough
and no extra key is needed. But there are some exceptions.
@@ -337,7 +340,7 @@
users it's a good idea to let the program chose the key size (in bits).
The default settings should be secure enough for most purposes.
- at subsection Adding a new user ID
+ at subsection Adding a new User ID
If you got a new email account, it's propably a good idea to
add these new account to your key also. For example:
@@ -353,7 +356,7 @@
Now email programs are able to associate this address with your
key when somebody wants to send you a protected mail to this account.
- at subsection Adding a photographic ID
+ at subsection Adding a new Photographic ID
With this function you can add a photo to your public. It will be
displayed in the key property dialog.
@@ -362,7 +365,7 @@
in the dialog carefully to make sure the photo has a proper size
(file, height and weight).
- at subsection Adding a new designated revoker
+ at subsection Adding a new Designated Revoker
If you want to allow another key to revoke your own key, this
might be useful if you lost your secret or a simliar situation,
you can use this function to add a designated revoker to your key.
@@ -396,4 +399,44 @@
a key from a file in general, just drag the file and drop it
into the Key Manager window or use "Key" -> "Import...".
+ at subsection Sign a Public Key
+If you verified that a key really belongs to its owner, you
+should sign the key to integrate it into your Web of Trust
+and also to mark the key as valid in your keyring. Do not sign
+a key you just got via email with the request to sign it. Anybody
+can create a key with your (or better ANY) name, these information
+are no hint to whom the key really belongs. You can check a key
+by meeting or calling the key owner and verify the key fingerprint
+of the key with the one published by the key owner. Additional checks
+should be to watch at his driver license or the identity card to make
+sure that name of the key matches the name of the key owner. After
+this procedure is done, you can open the Key Manager, select the
+right key and either use the context menu "Sign Key" or use the
+toolbar button.
+
+The next dialog will summarize the key information and some
+additional options. For example if the signature should be
+local or exportable. Local means the signature will be stripped
+if you export the key and no one else except you can use it to
+calculate the validity. If you mark the signature exportable,
+any other user can see and use it. Now you can select the key
+you want to use to sign and enter the passphrase. Confirm with "OK"
+and the key will be signed. Now the validity of the new key is
+"Full". It is propably a good idea to set the ownertrust of the
+key. For a detailled description, see the chapter "Key Ownertrust".
+
+ at subsection Key Ownertrust
+First we should explain what the ownertrust of a key is. The ownertrust
+is a measurement how much you trust somebody to certify and check keys
+of other people. For example, if you know that Bob is really the owner
+of the key, you should sign it. But he is also known to sign other keys
+without checking the idenity of the other key owner. Values for the
+ownertrust are 1) Don't Know 2) Don't Trust 3) Marginal 4) Full
+and thus you should propably use an ownertrust value like "Marginal".
+But this is a personal decision and stored in a separate file and
+never exported with the public keys. For further information, please
+take a look into the GNU Privacy Handbook.
+Just a last work on Key Pairs, they are automatically marked as
+"Ultimate" because the key belongs to you and you trust it implicit.
+
@bye
Modified: trunk/PTD/resource.rc
===================================================================
--- trunk/PTD/resource.rc 2006-06-12 13:40:21 UTC (rev 226)
+++ trunk/PTD/resource.rc 2006-06-14 06:57:57 UTC (rev 227)
@@ -47,14 +47,14 @@
VALUE "Comments", "This is free software under the tems of the GNU GPL V2\0"
VALUE "CompanyName", "\0"
VALUE "FileDescription", "PTD - Privacy Tray Dynamic\0"
- VALUE "FileVersion", "1.0.0-pre0\0"
+ VALUE "FileVersion", "1.0.0-pre1\0"
VALUE "InternalName", "PTD\0"
VALUE "LegalCopyright", "Copyright © 2006 Timo Schulz\0"
VALUE "LegalTrademarks", "\0"
VALUE "OriginalFilename", "PTD.dll\0"
VALUE "PrivateBuild", "\0"
VALUE "ProductName", "PTD\0"
- VALUE "ProductVersion", "1.0.0-pre0\0"
+ VALUE "ProductVersion", "1.0.0-pre1\0"
VALUE "SpecialBuild", "\0"
END
END
Modified: trunk/Src/WinPT-en.rc
===================================================================
--- trunk/Src/WinPT-en.rc 2006-06-12 13:40:21 UTC (rev 226)
+++ trunk/Src/WinPT-en.rc 2006-06-14 06:57:57 UTC (rev 227)
@@ -1978,14 +1978,14 @@
VALUE "Comments", "This is free software under the terms of the GNU GPL v2\0"
VALUE "CompanyName", "\0"
VALUE "FileDescription", "Windows Privacy Tray (WinPT)\0"
- VALUE "FileVersion", "1.0.0-pre0\0"
+ VALUE "FileVersion", "1.0.0-pre1\0"
VALUE "InternalName", "WinPT\0"
VALUE "LegalCopyright", " Copyright (C) 2006 Timo Schulz\0"
VALUE "LegalTrademarks", "\0"
VALUE "OriginalFilename", "WinPT.exe\0"
VALUE "PrivateBuild", "\0"
VALUE "ProductName", "Windows Privacy Tray\0"
- VALUE "ProductVersion", "1.0.0-pre0\0"
+ VALUE "ProductVersion", "1.0.0-pre1\0"
VALUE "SpecialBuild", "\0"
END
END
Modified: trunk/TODO
===================================================================
--- trunk/TODO 2006-06-12 13:40:21 UTC (rev 226)
+++ trunk/TODO 2006-06-14 06:57:57 UTC (rev 227)
@@ -3,6 +3,10 @@
Finally, we are close to release 1.0.0. Make a feature freeze,
fix all serious tracker items and do intensive tests.
+ * set imported private keys automatically to "ultimate" ownertrust?
+ + lock the program during the key caching phase to avoid
+ problems when the program tries to access the, not yet
+ finished, key cache object.
+ check native language support with non-admin accounts.
* there is a problem with the +E hotkey in EURO countries.
- migrate keyserver code to use the HTTP class.
Modified: trunk/configure.ac
===================================================================
--- trunk/configure.ac 2006-06-12 13:40:21 UTC (rev 226)
+++ trunk/configure.ac 2006-06-14 06:57:57 UTC (rev 227)
@@ -15,7 +15,7 @@
# Version number: Remember to change it immediately *after* a release.
# Add a "-cvs" prefix for non-released code.
-AC_INIT(WinPT, 1.0.0pre0, http://www.winpt.org)
+AC_INIT(WinPT, 1.0.0pre1-cvs, http://www.winpt.org)
NEED_GPG_VERSION=1.4.2
NEED_GPGME_API=1
NEED_GPGME_VERSION=1.1.1
More information about the Winpt-commits
mailing list