diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/DETAILS | 14 | ||||
| -rw-r--r-- | doc/README.W32 | 30 |
2 files changed, 24 insertions, 20 deletions
diff --git a/doc/DETAILS b/doc/DETAILS index a75ca663f..aefc8adfd 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -11,6 +11,7 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0::: sec = secret key ssb = secret subkey (secondary key) uid = user id (only field 10 is used). + sig = signature fpr = fingerprint: (fingerprint is in field 10) pkd = public key data (special field format, see below) @@ -47,7 +48,9 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0::: information may follow in some future versions. 10. Field: User-ID. The value is quoted like a C string to avoid control characters (the colon is quoted "\x3a"). -11. Field: Signature class +11. Field: Signature class. This is a 2 digit hexnumber followed by + either the letter 'x' for an exportable signature or the + letter 'l' for a local-only signature. 12. Field: Key capabilities: e = encrypt s = sign @@ -56,9 +59,12 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0::: addition to these letters, uppercase version of the letter to denote the _usable_ capabilities of the entire key. -All dates are displayed in the format yyyy-mm-dd unless you use the option ---fixed-list-mode in which case they are dispplay as seconds since epoch. -More fields may be added later. +All dates are displayed in the format yyyy-mm-dd unless you use the +option --fixed-list-mode in which case they are displayed as seconds +since Epoch. More fields may be added later, so parsers should be +prepared for this. When parsing a number the parser should stop at the +first non-number character so that additional information can later be +added. If field 1 has the tag "pkd", a listing looks like this: pkd:0:1024:B665B1435F4C2 .... FF26ABB: diff --git a/doc/README.W32 b/doc/README.W32 index 7e0b569e3..94d745fca 100644 --- a/doc/README.W32 +++ b/doc/README.W32 @@ -1,18 +1,10 @@ This is a binary version of GnuPG for MS-Windows 95, 98, WNT and W2000. - -PLEASE READ THE FOLLOWING PARAGRAPH CAREFULLY: - -If you have a bug report, please post it to the mailing list -<[email protected]>. Please don't send me private mail -regarding this version of GnuPG; I am already spending too much -time on answering the same and same questions over and over. -I can improve GnuPG much faster if I don't have to answer -questions in private mail. You can post to the mailing list -without prior subscribing (but please request to CC you if you want -to get an answer). - - +A FAQ comes with this package and a probably more recent one can be +found online at http://www.gnupg.org/faq.html. See +http://www.gnupg.org/docs-mls.html for a list of mailing lists. In +particular the list [email protected] might be useful to answer +questions - but please read the FAQ first. Installation instructions: -------------------------- @@ -34,7 +26,7 @@ Internationalization support: ----------------------------- 1. Decide where to store the translation files for your language. Here we assume the directory "c:/gnu/locale/fr" - 2. Set the directory with the translations into the Registry under the key: + 2. Set the directory with the translations into the Registry under the key: \\HKEY_CURRENT_USER\Control Panel\Mingw32\NLS\MODir (Example entry: "c:/gnu/locale/fr") 3. Select which language to use and copy the currect translation file @@ -53,7 +45,13 @@ How to build it from the source: This version has been build with the Mingw32/CPD kit using the latest stable version of GnuPG. -First get the source: It is available at +First get the source: It has to be available at the same location you +found this binary package - if not you should have received a written +offer to get the source delivered to you See the file COPYING (section +3) for details. + +If you got this package from its canonical place (ftp.gnupg.org), the +source is available at: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.0.n.tar.gz @@ -64,7 +62,7 @@ or for snapshots (with a letter appended to the version number) this is the same source as for the Unix version. If your binary version of GnuPG is called something like gnupg-w32-1.0.4-1.zip, you should find a patch file named gnupg-w32-1.0.4-1.0.4-1.diff.gz at the -same location, which has to ne applied to the stock gpg source file. +same location, which has to be applied to the stock gpg source file. Instructions are at the top of this file. To build it, you need the MingW32/CPD kit, which is available at |