Re: Signing a key (meaning)

2011-04-08 Thread Jan Janka
> But if an attacker puts his e-mail address on a key he claims to be > mine, he won't get my mail sent to (or encrypted to) him. If someone somehow gets that key, reads your name in the ID and relies on that name he might sent mail intented for you to the attacker's email address, that might ev

default keyserver-options [was: Re: keys not available for signed messages in this maillist]

2011-04-08 Thread Daniel Kahn Gillmor
On 04/08/2011 02:19 PM, John Clizbe wrote: > There are additional options for the keyserver-options line. I recommend > adding > ' include-subkeys include-revoked import-clean'. See the gpg man page. Thanks for these pointers, John. If you think these are good options, maybe we should advocate f

Re: Signing a key (meaning)

2011-04-08 Thread Daniel Kahn Gillmor
On 04/08/2011 06:02 PM, Jan Janka wrote: > I think there's no benefit, because everybody who issueses a key (even an > attacker) wants to receive information encrypted with that key, - otherwise > he wouldn't issue it. Thus he will place an email address in the ID he has > access to. So I think

Re: Signing a key (meaning)

2011-04-08 Thread Jan Janka
>> I wonder how I can check whether the email >>address in the ID realy belongs to the keyowner. >You can only check whether the key owner "has access" >to the email address. You cannot check whether this >access is in any way exclusive, legit or whatever. I think so, but WHAT benefit (concerning

Re: Do not conflate key+userID certification with "vouching"

2011-04-08 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi On Friday 8 April 2011 at 8:35:56 PM, in , Daniel Kahn Gillmor wrote: > Or, more simply, An OpenPGP certification is "vouching > for someone's identity"; it is not "vouching for > someone". The meaning and implications of "vouching for" someb

Re: Do not conflate key+userID certification with "vouching"

2011-04-08 Thread Daniel Kahn Gillmor
On 04/08/2011 02:38 PM, Grant Olson wrote: > Two definitions of vouch: > > 1. Assert or confirm as a result of one's own experience that something > is true or accurately so described. > 2. Confirm that someone is who they say they are or that they are of > good character: "someone could vouch fo

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Grant Olson
On 4/8/11 2:50 PM, Bernhard Kleine wrote: > > I am quite sure that Grant Olson's key is on the keyserver, thus there > is no matter of hiding it, as robert j.hansen suggested. however, i > wonder why i can't retrieve it. > > gpg --search-keys A18A54D > gpg: Suche nach "A18A54D" von hkp Server po

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Bernhard Kleine
Am Freitag, den 08.04.2011, 14:09 -0500 schrieb John Clizbe: > Key IDs are 8 hex digits. You have typed 7. Add the '6' at the end :-) > > sks@yogi:~$ gpg --keyserver yogi --search-keys 0xA18A54D6 > gpg: searching for "0xA18A54D6" from hkp server yogi > (1) Grant T. Olson (pikimal) >

Re: keys not available for signed messages in this maillist

2011-04-08 Thread John Clizbe
Bernhard Kleine wrote: > > I am quite sure that Grant Olson's key is on the keyserver, thus there > is no matter of hiding it, as robert j.hansen suggested. however, i > wonder why i can't retrieve it. > > gpg --search-keys A18A54D > gpg: Suche nach "A18A54D" von hkp Server pool.sks-keyservers.n

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Bernhard Kleine
Am Freitag, den 08.04.2011, 13:19 -0500 schrieb John Clizbe: > John Clizbe wrote: > > Bernhard Kleine wrote: > >> Hi, > >> > >> i wonder whether the keys from several members of this maillist should > >> be available from the keyserver. e.g. Grant Olson signs all his messages > >> here. evolution

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Bernhard Kleine
Am Freitag, den 08.04.2011, 11:29 -0500 schrieb John Clizbe: > Bernhard Kleine wrote: > > Hi, > > > > i wonder whether the keys from several members of this maillist should > > be available from the keyserver. e.g. Grant Olson signs all his messages > > here. evolution and gpg on ubuntu, however,

Re: Do not conflate key+userID certification with "vouching" [was: Re: How to verify the e-mail address when certifying OpenPGP User IDs]

2011-04-08 Thread Grant Olson
On 4/8/11 2:00 PM, Daniel Kahn Gillmor wrote: > On 04/07/2011 09:37 PM, Grant Olson wrote: >> Keep in mind that the web-of-trust isn't the mafia. If you 'vouch' for >> someone and they turn out to be a rat, nobody's going to two bullets in >> your chest, and one in your head. > > "Vouching" for s

Re: keys not available for signed messages in this maillist

2011-04-08 Thread John Clizbe
John Clizbe wrote: > Bernhard Kleine wrote: >> Hi, >> >> i wonder whether the keys from several members of this maillist should >> be available from the keyserver. e.g. Grant Olson signs all his messages >> here. evolution and gpg on ubuntu, however, fail to retrieve the public >> key from the ser

Do not conflate key+userID certification with "vouching" [was: Re: How to verify the e-mail address when certifying OpenPGP User IDs]

2011-04-08 Thread Daniel Kahn Gillmor
On 04/07/2011 09:37 PM, Grant Olson wrote: > Keep in mind that the web-of-trust isn't the mafia. If you 'vouch' for > someone and they turn out to be a rat, nobody's going to two bullets in > your chest, and one in your head. "Vouching" for someone usually means that you think you can rely on the

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Robert J. Hansen
On 4/8/11 12:43 PM, Andrew Long wrote: > 'Should' and 'Must' have specific meanings within most RFC's. SHOULD and MUST do. They're presented in all-caps in RFCs to make sure people know they're being used in a formal context as opposed to a conversational English context. If you want to say cert

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Andrew Long
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 8 Apr 2011, at 16:23, Robert J. Hansen wrote: > On 4/8/11 10:25 AM, Bernhard Kleine wrote: >> > "Should" is maybe the wrong word to use. I've never seen "should" mean > anything other than, "I want" or "I expect." 'Should' and 'Must' have

Re: keys not available for signed messages in this maillist

2011-04-08 Thread John Clizbe
Bernhard Kleine wrote: > Hi, > > i wonder whether the keys from several members of this maillist should > be available from the keyserver. e.g. Grant Olson signs all his messages > here. evolution and gpg on ubuntu, however, fail to retrieve the public > key from the server: > > the message alway

Re: Set key to be default to sign/encrypt

2011-04-08 Thread Kevin
On Thu, Apr 07, 2011 at 09:10:45PM +0200 Also sprach Csabi: Hi! Thx your reply. I tried the following: gpg -u 4096R/626D791C --detach-sign t.txt The error is the same: gpg: skipped "4096R/626D791C": secret key not available gpg: signing failed: secret key not available I tried it with

Re: keys not available for signed messages in this maillist

2011-04-08 Thread Robert J. Hansen
On 4/8/11 10:25 AM, Bernhard Kleine wrote: > i wonder whether the keys from several members of this maillist should > be available from the keyserver. e.g. Grant Olson signs all his messages > here. evolution and gpg on ubuntu, however, fail to retrieve the public > key from the server: "Should" i

keys not available for signed messages in this maillist

2011-04-08 Thread Bernhard Kleine
Hi, i wonder whether the keys from several members of this maillist should be available from the keyserver. e.g. Grant Olson signs all his messages here. evolution and gpg on ubuntu, however, fail to retrieve the public key from the server: the message always reads: signature exists, however, the

Re: Signing a key (meaning)

2011-04-08 Thread Mark H. Wood
Sounds like some people could use a signature type which means: "I disclaim all signatures made by ". -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpp2yNFuADwp.pgp Description: PGP signature ___