...key belongs to ...

[Daniel Kahn Gillmor]

On 05/29/2010 08:47 PM, Dan Mahoney, System Admin wrote:
> On Sun, 30 May 2010, Michael D. Berger wrote:
>> Now in the context in which this is being used, there is no
>> uncertainty regarding key ownership, and the encryption is
>> part of a bash script.  The query stops the script.
>>
>> Therefore, how can I prevent this query?
> 
> Edit the trust of the key, and or sign it with a trust signature.

Please do not follow Dan Mahoney's suggestion here :/

The prompt you're trying to address is about fixing gpg's perceived
calculated validity of the key, *not* about how much you trust the owner
to make proper certifications.   Trust signatures or edited ownertrust
should not be used to adjust the validity of a single key's user ID,
since an adjustment like that will have other unintended consequences
(e.g. the holder of the key whose ownertrust is elevated will now be
able to fool you into thinking that other key+uid combinations are
actually valid).

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 892 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20100531/bd5ffe28/attachment.pgp>