Mailing List Archive

0.4.2 is out
Hi,

GnuPG 0.4.2 is now out.

ftp://ftp.guug.de/pub/gcrypt/gnupg-0.4.2.tar.gz (750k)

ftp://ftp.guug.de/pub/gcrypt/diffs/gnupg-0.4.2.diff.gz (150k)


See doc/HACKING for instructions on how to use anon-CVS.


* This is only a snapshot: There are still a few bugs.

* Fixed this huge memory leak.

* Redesigned the trust database: You should run "gpgm --check-trustdb".
New command --update-trustdb, which adds new key from the public
keyring into your trustdb

* Fixed a bug in the armor code, leading to invalid packet errors.
(a workaround for this was to use --no-armor). The shorten line
length (64 instead of 72) fixes a problem with pgp5 and keyservers.

* comment packets are not anymore generated. "--export" filters
them out. One Exception: The comment packets in a secret keyring
are still used because they carry the factorization of the public
prime product.

* --import now only looks for KEYBLOCK headers, so you can now simply
remove the "- " in front of such a header if someone accdently signed
such a message or the keyblock is part of a cleartext signed message.

* --with-colons now lists the key expiration time and not anymore
the valid period.

* Some keyblocks created with old releases have a wrong sequence
of packets, so that the keyservers don't accept these keys.
Simply using "--edit-key" fixes the problem.

* New option --force-v3-sigs to generate signed messages which are
compatible to PGP 5.

* Add some code to support DLD (for non ELF systems) - but this is
not tested because my BSD box is currently broken.

* New command "expire" in the edit-key menu.



Have fun.


Werner
Re: 0.4.2 is out [ In reply to ]
Any idea when the new strong RNG code for systems without /dev/random
will be integrated into GnuPG? Is anyone working on that?

--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
Re: 0.4.2 is out [ In reply to ]
"Paul D. Smith" <psmith@BayNetworks.COM> writes:

> Any idea when the new strong RNG code for systems without /dev/random
> will be integrated into GnuPG? Is anyone working on that?

I'm waiting for a response from Peter - but it's now spring down there
...

Werner
Re: 0.4.2 is out [ In reply to ]
%% Werner Koch <wk@isil.d.shuttle.de> writes:

wk> "Paul D. Smith" <psmith@BayNetworks.COM> writes:

>> Any idea when the new strong RNG code for systems without /dev/random
>> will be integrated into GnuPG? Is anyone working on that?

wk> I'm waiting for a response from Peter - but it's now spring down there

A response from Peter about what, exactly?

Perhaps, like me, he's just not aware you're waiting for him to respond :)

--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
Re: 0.4.2 is out [ In reply to ]
>>>>> "Werner" == Werner Koch "0.4.2 is out"
>>>>> Sun, 18 Oct 1998 17:37:06 +0200

Werner> * This is only a snapshot: There are still a few bugs.

Is this one?

[jam@athene jam]$ gpg --force-v3-sigs -sat <foo | gpg
[[ ... ]]
gpg: Signature made Mon Oct 19 14:55:01 1998 ED using DSA key ID BFE25F2F
gpg: BAD signature from "John A. Martin <jam@acm.org>"
[jam@athene jam]$ gpg -sat <foo | gpg
[[ ... ]]
gpg: Signature made Mon Oct 19 14:58:37 1998 ED using DSA key ID BFE25F2F
gpg: Good signature from "John A. Martin <jam@acm.org>"

jam
Re: 0.4.2 is out [ In reply to ]
"John A. Martin" <jam@jamux.com> writes:

> Werner> * This is only a snapshot: There are still a few bugs.
>
> Is this one?

Yep.

Thanks.

Werner
Re: 0.4.2 is out [ In reply to ]
On Mon, Oct 19, 1998 at 03:52:16PM -0400, John A. Martin wrote:
> >>>>> "Werner" == Werner Koch "0.4.2 is out"
> >>>>> Sun, 18 Oct 1998 17:37:06 +0200
>
> Werner> * This is only a snapshot: There are still a few bugs.
>
> Is this one?
>
> [jam@athene jam]$ gpg --force-v3-sigs -sat <foo | gpg
> [[ ... ]]
> gpg: Signature made Mon Oct 19 14:55:01 1998 ED using DSA key ID BFE25F2F
> gpg: BAD signature from "John A. Martin <jam@acm.org>"
> [jam@athene jam]$ gpg -sat <foo | gpg
> [[ ... ]]
> gpg: Signature made Mon Oct 19 14:58:37 1998 ED using DSA key ID BFE25F2F
> gpg: Good signature from "John A. Martin <jam@acm.org>"

Try --digest-algo sha1

And GPG should be happy.

--
Brian Moore | "The Zen nature of a spammer resembles
Sysadmin, C/Perl Hacker | a cockroach, except that the cockroach
Usenet Vandal | is higher up on the evolutionary chain."
Netscum, Bane of Elves. Peter Olson, Delphi Postmaster
Re: 0.4.2 is out [ In reply to ]
brian moore <bem@cmc.net> writes:

> Try --digest-algo sha1
>
> And GPG should be happy.

I changed the way force_v3_sigs is handled.
Re: 0.4.2 is out [ In reply to ]
>"Paul D. Smith" <psmith@BayNetworks.COM> writes:
>
>>Any idea when the new strong RNG code for systems without /dev/random
>>will be integrated into GnuPG? Is anyone working on that?
>
>I'm waiting for a response from Peter - but it's now spring down there ...

I've got two conferences I've been preparing for, so I haven't had time to
release the new dual-license version (with a choice of use under the existing
conditions or the GPL). In the meantime go ahead and use the existing code as
if it were under the dual-license terms, I'll get a new version out when I get
back from the US in early November.

Peter.
Re: 0.4.2 is out [ In reply to ]
At 5:37 PM 10/18/98, Werner Koch wrote:
> New command --update-trustdb, which adds new key from the public
> keyring into your trustdb

gpgm -h sez:

--update-trustdb [NAMES]

I thought NAMES would just be, say, an e-mail address on a public key that
I wanted to be trusted, but it don't like that:

usage: gpgm [options] --update-trustdb

Yes, I'm moving to 0.4.3, but figured I'd go through 0.4.2 along the way. :-)

-- "TANSTAAFL" Rich lynch@cognitivearts.com webmaster@ and www. all of:
R&B/jazz/blues/rock - jademaze.com music industry org - chatmusic.com
acoustic/funk/world-beat - astrakelly.com sculptures - olivierledoux.com
my own nascent company - l-i-e.com cool coffeehouse - uncommonground.com
Re: 0.4.2 is out [ In reply to ]
Richard Lynch <lynch@cognitivearts.com> writes:
>
> usage: gpgm [options] --update-trustdb
>
> Yes, I'm moving to 0.4.3, but figured I'd go through 0.4.2 along the way. :-)

I forgot to rewrite one function (i only removed the old code and put
a comment, that this has to be rewritten but without my usual
"FIXME"). It will be in the next release and validation of
trust will be must faster.

Sorry,

Werner