[Kolab-devel] [issue3615] KMail evaluation all uids of a key it trieds to encrypt to, leading to missleading warnings

[Bernhard Reiter]

New submission from Bernhard Reiter <bernhard at intevation.de>:

I am getting a confusing warning when trying to encrypt
to an email address where the key has several uids
and some are not fully valid.

My expectation is that only the uid in question is checked against
validity. 

To reproduce this issue you would need to have a key with several
uids that some have a valididy of 0 (aka unkown) in gpg2 --edit-key.
E.g. for me I can demostrate this on the key of Matthias (attached).

I have deleted one uid which I had "unknown", and now I cannot reproduce:
LANG=C gpg2 --edit-key mk at fsfe.org
gpg (GnuPG) 2.0.11; 
pub  1024D/8EF520D1  created: 2002-11-21  expires: never       usage: SC
                     trust: unknown       validity: full
sub  1024g/64A4C81B  created: 2002-11-21  expires: never       usage: E
sub  1024R/1216110F  created: 2005-10-13  expires: never       usage: A
sub  1024R/A5D6BFBC  created: 2005-10-13  expires: never       usage: S
sub  1024R/323CE763  created: 2005-10-13  expires: never       usage: E
[  full  ] (1). Matthias Kirschner <mk at mbwg.de>
[  full  ] (2)  Matthias Kirschner <mk at office.fsfeurope.org>
[  full  ] (3)  Matthias Kirschner <matze at mbwg.de>
[  full  ] (4)  Matthias Kirschner <matze at difficulties.de>
[  full  ] (5)  Matthias Kirschner <mk at fsfe.org>
[ revoked] (6)  Matthias Kirschner <matthias.kirschner at gmx.de>
[ revoked] (7)  Matthias Kirschner <greve-assist at fsfeurope.org>
[ revoked] (8)  Matthias Kirschner <matthias.kirschner at uni-konstanz.de>

Importing this uid again:
gpg2 --import tmp/mk.key
 LANG=C gpg2 --edit-key mk at fsfe.org
gpg (GnuPG) 2.0.11;
pub  1024D/8EF520D1  created: 2002-11-21  expires: never       usage: SC
                     trust: unknown       validity: full
sub  1024g/64A4C81B  created: 2002-11-21  expires: never       usage: E
sub  1024R/1216110F  created: 2005-10-13  expires: never       usage: A
sub  1024R/A5D6BFBC  created: 2005-10-13  expires: never       usage: S
sub  1024R/323CE763  created: 2005-10-13  expires: never       usage: E
[  full  ] (1). Matthias Kirschner <mk at mbwg.de>
[  full  ] (2)  Matthias Kirschner <mk at office.fsfeurope.org>
[  full  ] (3)  Matthias Kirschner <matze at mbwg.de>
[  full  ] (4)  Matthias Kirschner <matze at difficulties.de>
[  full  ] (5)  Matthias Kirschner <mk at fsfe.org>
[ revoked] (6)  Matthias Kirschner <matthias.kirschner at gmx.de>
[ revoked] (7)  Matthias Kirschner <greve-assist at fsfeurope.org>
[ revoked] (8)  Matthias Kirschner <matthias.kirschner at uni-konstanz.de>
[ unknown] (9)  Matthias Kirschner <kirschner at fsfeurope.org>

Now I am getting the missleading warning when trying to encrypt, e.g.
to mk at fsfe.org. There should not be a warning as "mk at fsfe.org" is a fully valid 
uid.

I think it should be possible to create a test-setup for you,
just delete your signatures on one of the uids for a key until you
have something like above.

----------
assignedto: allen
files: mk.key
messages: 20164
nosy: allen, bernhard, marc, till
priority: bug
status: unread
title: KMail evaluation all uids of a key it trieds to encrypt to, leading to missleading warnings
topic: crypto, enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3615>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mk.key
Type: application/octet-stream
Size: 14332 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090512/b514c462/attachment.obj>