Snapshot release 0.4.2

doc/DETAILS

@@ -364,6 +364,14 @@ Other Notes
       to keep them small.
 
 
+Supported targets:
+------------------
+      powerpc-unknown-linux-gnu  (linuxppc)
+      hppa1.1-hp-hpux10.20
+
+
+
+
 
 
 

doc/FAQ

@@ -103,6 +103,12 @@
     is choosen.  You may add an type 16 ElGamal key to your public
     key which is easy as your key signatures are still valid.
 
+ Q: Why is PGP 5.x not able to verify my messages.
+ A: PGP 5.x does not accept V4 signatures for data material but
+    OpenPGP requires generation of V3 signatures for all kind of
+    data.  Use the option "--force-v3-sigs" to generate V3 signatures
+    for data.
+
  Q: I can't delete a user id because it is already deleted on my
     public keyring.
  A: Because you can only select from the public key ring, there is

doc/OpenPGP

@@ -1,4 +1,4 @@
-		    GNUPG and OpenPGP
+		    GnuPG and OpenPGP
 		    =================
 
    The current OpenPGP draft expires 1999-02.
@@ -22,17 +22,21 @@
 
   Compatibility Notes
   ===================
-   GNUPG (>=0.4.1) is in compliance with OpenPGP despite these exeptions:
+   GnuPG (>=0.4.1) is in compliance with OpenPGP despite these exeptions:
 
     * (5.1) The critical bit in signature subpackets is currently
       ignored.	This will be fixed soon.
 
-    * (5.3) GNUPG has an option to use simple S2K for "Symmetric-Key
+
+    * (5.2) GnuPG generates V4 signatures for all V4 keys.  The option
+      --force-v3-sigs allows to override.
+
+    * (5.3) GnuPG has an option to use simple S2K for "Symmetric-Key
       Encrypted Session-Key Packets"; however a warning message is
       issued if this option is active.
 
     * (5.5.2) states that an implementaion MUST NOT create a v3 key
-      with an algorithm other than RSA.  GNUPG has an option to
+      with an algorithm other than RSA.  GnuPG has an option to
       create an ElGamal key in a v3 packet; the properties of such
       a key are as good as a v4 key.  RFC1991 does not specifiy how
       to create fingerprints for algorithms other than RSA and so it
@@ -46,7 +50,7 @@
       due to patent problems.
 
     * (12.1) states that an implementaion MUST NOT use a symmetric
-      algorithm which is not in the preference list.  GNUPG has an
+      algorithm which is not in the preference list.  GnuPG has an
       option to override this.
 
     * A special format of partial packet length exists for v3 packets

doc/gpg.1pod

@@ -128,6 +128,11 @@ B<--edit-key> I<name>
        Add a subkey to this key.
     B<delkey>
        Remove a subkey.
+    B<expire>
+       Change the key expiration time.	If a key is
+       select, the time of this key will be changed.
+       With no selection the key expiration of the
+       primary key is changed.
     B<passwd>
        Change the passphrase of the secret key.
     B<uid> I<n>
@@ -303,7 +308,16 @@ B<--status-fd> I<n>
     Write special status strings to the file descriptor I<n>.
 
 B<--no-comment>
-    Do not write comment packets.
+    Do not write comment packets.  This option affects only
+    the generation of secret keys.  Output of option packets
+    is disabled since version 0.4.2.
+
+B<--comment> I<string>
+    Use I<string> as comment string in clear text signatures.
+
+B<--set-filename> I<string>
+    Use I<string> as the name of file which is stored in
+    messages.
 
 B<--completes-needed> I<n>
     Number of completely trusted users to introduce a new
@@ -373,6 +387,15 @@ B<--passphrase-fd> I<n>
     can only be used if only one passphrase is supplied.
     B<Don't use this option if you can avoid it>
 
+B<--rfc1991>
+    Try to be more RFC1991 (PGP 2.x) compliant.
+
+B<--force-v3-sigs>
+    OpenPGP states that a implemenation should generate
+    v4 signatures but PGP 5.x does only recognize such
+    signatures on key material.  This options forces
+    v3 signatures for signatures on data.
+
 B<--no-verbose>
     Reset verbose level to 0.