Mailing List Archive: 0.9.0 --clearsign does not generate correct armor

0.9.0 --clearsign does not generate correct armor

Dec 27, 1998, 10:31 AM

Post #1 of 4 (286 views)

Moin,

i think that's a bug:

gpg --clearsig anyfile

and then

gpg anyfile.asc

results in "BAD signature". Thats maybe caused by a missing empty line
after the comment: ?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.0 (GNU/Linux)
Comment: For info see www.gnupg.org
iEYEARECAAYFAjaGa7QACgkQ9osbfOpXJPjLKgCgyRDnhPblT5WMYREshIQiY7E7
lXoAniAOP0I4tqbmZtT/jnucCke4xdCo
=j2Rs
-----END PGP SIGNATURE-----

(Indented by one by me)

Can someone verify this, please?

Gruss,
Walter

--
Walter Koch Hochdahl am Neandertal
walterk@mail.dip.de ham:dg9ep@db0iz
http://home.pages.de/~dg9ep/ qrv:db0iz-9

Re: 0.9.0 --clearsign does not generate correct armor [ In reply to ]

wk at isil

Dec 27, 1998, 1:38 PM

Post #2 of 4 (285 views)

Permalink

Walter Koch <walterk@dip.de> writes:

> results in "BAD signature". Thats maybe caused by a missing empty line
> after the comment: ?

Workaround:

echo "comment \"see www.gnupg.org\"" >>~/.gnupg/options

Re: 0.9.0 --clearsign does not generate correct armor [ In reply to ]

cloos at jhcloos

Dec 27, 1998, 2:52 PM

Post #3 of 4 (287 views)

Permalink

>>>>> "Werner" == Werner Koch <wk@isil.d.shuttle.de> writes:

Werner> Workaround:

Werner> echo "comment \"see www.gnupg.org\"" >>~/.gnupg/options

Speaking of which, would using http://www.gnupg.org rather than just
www.gnupg.org break anything? In my tests w/ 0.9.0 everything works
but I do not have pgp installed to compare. (It is the colon in the
comment that gives me concern.)

Having a more complete URL will allow MUAs and NUAs to recognize it
and make it a clickable button. Sounds like better advertising, eh?

-JimC
--
James H. Cloos, Jr. <http://www.jhcloos.com/cloos/pgp_public_key.txt>
<cloos@jhcloos.com> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6

Re: 0.9.0 --clearsign does not generate correct armor [ In reply to ]

bem at cmc

Dec 27, 1998, 3:11 PM

Post #4 of 4 (289 views)

Permalink

On Sun, Dec 27, 1998 at 03:52:54PM -0600, James H. Cloos Jr. wrote:
> >>>>> "Werner" == Werner Koch <wk@isil.d.shuttle.de> writes:
>
> Werner> Workaround:
>
> Werner> echo "comment \"see www.gnupg.org\"" >>~/.gnupg/options
>
> Speaking of which, would using http://www.gnupg.org rather than just
> www.gnupg.org break anything? In my tests w/ 0.9.0 everything works
> but I do not have pgp installed to compare. (It is the colon in the
> comment that gives me concern.)

Shouldn't be a problem... I've had a colon in mine for ages. :)

> Having a more complete URL will allow MUAs and NUAs to recognize it
> and make it a clickable button. Sounds like better advertising, eh?

Indeed. I'm pondering signing my Usenet posts partly for that reason.
(And partly because it's trivial to forge Usenet posts and there are a
couple forgery attacks going on at the moment.)

--
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