no-ks-modify effect on signature uploads

[Hauke Laging]

Hello,

a few weeks ago we had a discussion about the no-ks-modify flag (being not 
reliably supported by the keyservers yet).

It certainly makes a difference whether you can accidentally ignore this flag 
or have to ignore it intentionally. This raises the question (I admit I was 
too lazy to test that myself) whether gpg ignores this flag. Does gpg upload 
signatures for other people's key which have this flag? The keyservers don't 
do crypto checks but gpg could, of course. IMHO it would make sense for gpg to 
reject uploads in these cases.


Hauke
-- 
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20100811/29392ea0/attachment.pgp>