From 47e7e7bbbd66435f605b45cf1b6c41a9daa6507b Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Fri, 25 Oct 2002 09:55:16 +0000 Subject: [PATCH] * README.W32: Add blurb on how to create a ZIP file, changed requirement for mingw32 to 0.3.2. --- doc/ChangeLog | 5 +++++ doc/README.W32 | 19 ++++++++++--------- doc/gpg.texi | 30 +++++++++++++++++++++++------- 3 files changed, 38 insertions(+), 16 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 2aff30d7c..97e7cd54f 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2002-10-25 Werner Koch + + * README.W32: Add blurb on how to create a ZIP file, changed + requirement for mingw32 to 0.3.2. + 2002-10-24 David Shaw * gpg.sgml: Document --refresh-keys. diff --git a/doc/README.W32 b/doc/README.W32 index 61aa05f0e..f4d6e9f86 100644 --- a/doc/README.W32 +++ b/doc/README.W32 @@ -1,4 +1,5 @@ -This is a binary version of GnuPG for MS-Windows 95, 98, WNT and W2000. +This is a binary version of GnuPG for MS-Windows 95, 98, WNT, W2000 +and XP. A FAQ comes with this package and a probably more recent one can be found online at http://www.gnupg.org/faq.html. See @@ -9,8 +10,8 @@ questions - but please read the FAQ first. Installation instructions: -------------------------- 1. Unpack the ZIP archive (alright, you already did this). - 2. Copy "gpg.exe" and "gpgv.exe" to some place where you - usually store your binaries. + 2. Copy "gpg.exe", "gpgv.exe" and "gpgkeys_ldap.exe" to a place + where you usually store your binaries. 3. Create a directory "c:\gnupg" (or any other as you like) 4. If you did not use the default directory "c:\gnupg", you should enter a string with the directory into the Registry @@ -72,7 +73,7 @@ Instructions are at the top of this file. To build it, you need the MingW32/CPD kit, which is available at - ftp://ftp.gnupg.org/people/werner/cpd/mingw32-cpd-0.3.0.tar.gz + ftp://ftp.gnupg.org/people/werner/cpd/mingw32-cpd-0.3.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/gcc-core-2.95.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/binutils-2.9.1.tar.gz @@ -86,8 +87,11 @@ After you have installed this environment you should be able to do this: $ mingw32 strip g10/gpg.exe $ cp g10/gpg.exe /some_windows_drive/ -And everything hopefully works. - +And everything hopefully works. If there is a make problem in the +"po" directory you can eiterignore it or do a "touch po/all". To +build the distribtion ZIP file, you have to create a directory +"dist-w32" and run "scripts/mk-w32-dist" right after a successul make +run. Don't forget that MS-Windows ist just a temporary workaround until you can switch to a GNU system ;-) @@ -95,6 +99,3 @@ you can switch to a GNU system ;-) Be the source always with you. Werner - - - diff --git a/doc/gpg.texi b/doc/gpg.texi index 8d0b70c2d..fd20c2ae6 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -104,8 +104,10 @@ List all keys from the public keyrings, or just the ones given on the command line. @item ---list-secret-keys @code{names} -List all keys from the secret keyrings, or just the -ones given on the command line. +List all keys from the secret keyrings, or just the ones given on the +command line. A '#' after the letters 'sec' means that the secret key +is not usable (for example, if it was created via +---export-secret-subkeys). @item ---list-sigs @code{names} Same as ---list-keys, but the signatures are listed too. @@ -381,6 +383,12 @@ but does only the merging of new signatures, user-IDs and subkeys. Import the keys with the given key IDs from a keyserver. Option ---keyserver must be used to give the name of this keyserver. +@item ---refresh-keys @code{key IDs} +Request updates from a keyserver for keys that already exist on the +local keyring. This is useful for updating a key with the latest +signatures, user IDs, etc. Option ---keyserver must be used to give +the name of this keyserver. + @item ---search-keys @code{names} Search the keyserver for the given names. Multiple names given here will be joined together to create the search string for the keyserver. @@ -605,7 +613,8 @@ from, send keys to, and search for keys on. The format of the the type of keyserver: "hkp" for the Horowitz (or compatible) keyservers, "ldap" for the NAI LDAP keyserver, or "mailto" for the Horowitz email keyserver. Note that your particular installation of -GnuPG may have other keyserver types available as well. +GnuPG may have other keyserver types available as well. Keyserver +schemes are case-insensitive. Most keyservers synchronize with each other, so there is generally no need to send keys to more than one server. Using the command "host -l @@ -1075,7 +1084,8 @@ available, but the MIT release is a good common baseline. This option implies `---rfc1991 --no-openpgp --disable-mdc ---no-force-v4-certs --no-comment --escape-from-lines --force-v3-sigs ---no-ask-sig-expire --no-ask-cert-expire --cipher-algo IDEA ----digest-algo MD5 --compress-algo 1' +---digest-algo MD5 --compress-algo 1'. It also disables --textmode +when encrypting. @item ---no-pgp2 Resets the ---pgp2 option. @@ -1128,9 +1138,15 @@ changes the default hash algorithm for v3 RSA keys from MD5 to SHA-1. Reset the ---force-v4-certs option. @item ---force-mdc -Force the use of encryption with appended manipulation code. This is -always used with the newer ciphers (those with a blocksize greater -than 64 bit). +Force the use of encryption with a modification detection code. This +is always used with the newer ciphers (those with a blocksize greater +than 64 bits), or if the recipient key has one of those ciphers as a +preference. + +@item ---disable-mdc +Disable the use of the modification detection code. Note that by +using this option, the encrypted message becomes vulnerable to a +message modification attack. @item ---allow-non-selfsigned-uid Allow the import and use of keys with user IDs which are not