On Mon, Dec 18, 2000 at 10:11:07AM +0100, Thorsten Haude wrote:
>Moin,
>
>On 00-12-18, Joe Philipps wrote:
>You don't have to sign them, only to acknowledge their validity. For
>example, I would acknowledge any keys signed by 'ct magazine CERTIFICATE',
>because I know how nitpicky they are.
welllll.....I can think of two ways to get rid of the lack of verified
key message (the goal): use a bunch of trusted-key statements either
in options or on the command line, or sign each key w/ my key. It's
more of a "reduction of annoyance factor" than a truly important
program issue.
>>The thing is, I probably don't want to sign them because other than
>>trusting the keyserver, I cannot verify (well, would find it difficult to
>>verify) the individual keys.
>You don't have to sign them only to add them to your ring. Just add
>>them.
It's not so much the "add to keyring" that's the problem; it's the
message warning me about the fact that the signature has questionable
validity.
>On a related issue, your key is not on the servers:
>- - -
>[-- PGP-Ausgabe folgt (aktuelle Zeit: Mon Dec 18 09:50:15 2000) --]
>gpg: Unterschrift vom Mon 18 Dez 2000 06:29:09 CET, DSA Schlüssel ID FA029353
>gpg: Schlüssels FA029353 von wwwkeys.eu.pgp.net wird angefordert ...
>gpg: Schlüssel FA029353: Öffentlicher Schlüssel importiert
>gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
>gpg: importiert: 1
>gpg: FALSCHE Unterschrift von "Joe Philipps (Philipps family sig)
><[EMAIL PROTECTED]>"
>[-- Ende der PGP-Ausgabe --]
>- - -
>(The important line is the last one saying 'WRONG signature from (...)'.)
>What's wrong?
First, sorry, the only language I understand is English, and I've had
4 years of Spanish study (meaning I'm not exactly fluent but I
understand it some). I'm guessing that's German in your GPG message.
uhhhhhhhhhhhhhhhh....I've submitted to several, I thought to
wwwkeys.us.pgp.net, which I thought shared keys with the other ones.
What the heck...it can't hurt if I submit it to a few more :-). It
should be on keyserver.net (the one in my .sig block). You should
also be able to get it "manually" by downloading it from the Web site
listed in my .sig block.
Beyond that, I don't know if there's a transport problem or maybe a
content encoding problem. I'd like it if someone could then help me
track that down, please.
So that people with plain text mailers would have an easier time
verifying my emails, I usually have put on the "traditional"
option(s). But these days I'm paying more attention to that statement
in the manual about this format being deprecated :^) :^). Something
might be messed up since I switched back? Didn't undo all those
configurations?
>On another related issue: I failed to add this address to my key. This
>should be fixed now.
>
>Thorsten
--
Oooooo-oooo-oooo-ooooo, Oooooo-oooo-oooo-ooooo, Ooooo-weem-oh-wum-ooo-ayyy
In the jungle, the silicon jungle, the process sleeps tonight.
Joe Philipps <[EMAIL PROTECTED]>, http://www.philippsfamily.org/Joe/
public PGP/GPG key 0xFA029353 available via http://www.keyserver.net
PGP signature
