[Announce] GnuPG 1.3.6 released (development)

Atom 'Smasher' atom at suspicious.org
Sun May 23 09:38:22 CEST 2004

Hash: SHA1

FreeBSD 4.9-RELEASE #0

./configure --program-suffix=_1.3.6

no problems.


multiple comments are working!! soon, the comment in my signature will
span 2 lines and be fully compliant with rfc 2822:2.1.1


i'm too tired now to test this myself, but i'm curious... i'm assuming
that fetching keys will not work via https. if that's the case, and a key
uses a preferred keyserver that specifies https (or some other unknown or
unsupported protocol), does it fail gracefully or does it get ugly?

has anyone tried this?


generating keys in batch mode still doesn't write to keys to the keyrings
as it goes... dave, you said the fix was in for this, i'm not sure if that
means that it should be behaving differently in 1.3.6...?


- --default-cert-level


1.2.4 will use the specified level as a default, but still ASK what level
signature to issue... 1.3.6 does NOT ask, it just uses the supplied
default. that means that the default isn't *really* a default, but rather
the signature level is specified on the command line instead of

- --sign-key and --edit-key both seem to behave the same on this.

i like the old (interactive) way better.


man page says:
                   Show  any  preferred keyserver URL in the signature
                   being verified.  Defaults to no.

the default seems to be "yes".


past my bedtime.....



 PGP key - http://atom.smasher.org/pgp.txt
 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808

	"Nearly all men can stand adversity, but if you want
	 to test a man's character, give him power."
		-- Abraham Lincoln
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures


More information about the Gnupg-devel mailing list