[Announce] release candidate for 1.4.1 available

David Shaw dshaw at jabberwocky.com
Thu Feb 3 22:38:21 CET 2005

On Thu, Feb 03, 2005 at 01:21:39PM -0500, Charly Avital wrote:

> >  * New --rfc2440-text option which controls how text is handled in
> >    signatures.  This is in response to some problems seen with
> >    certain PGP/MIME mail clients and GnuPG version 1.4.0.  More
> >    details about this are available at
> >     
> > <http://lists.gnupg.org/pipermail/gnupg-users/2005-January/ 
> > 024408.html>
> Self-test correctly verified by two different MUAs that use gpg. When  
> verifying with PGP 8.1, bad signature (will inform the PGP people).

I'm not sure what didn't work here.  What did you verify with PGP 8.1?

> >  * New "import-unusable-sigs" and "export-unusable-sigs" tags for
> >    --import-options and --export-options.  These are on by
> >    default, and cause GnuPG to not import or export key signatures
> >    that are not usable (e.g. expired signatures).
> The wording is a bit confusing, *for me* that is:
> if the tag --import-unusable-sigs is on by default, how will that cause  
> GnuPG *not* to import key signatures that are not usable? It would seem  
> that it would cause GnuPG to import key signatures that are not usable.  
> Ditto for export. Sorry if this sounds dense.

This was a typo.  The options are *off* by default.


More information about the Gnupg-users mailing list