New submission from Marc Mutz <marc@klaralvdalens-datakonsult.se>:
There is this weird convention that the DN of an x.509 cert is in
key->uids->uid, and the email address(es) in key->uids->(next->)+uid, enclosed
in <angle brackets>. However, there is an "email" field in gpgme_userid_t,
which in these cases is NULL.
A more logical place would be that email field, of course, but it should be
extended to keep a list of emails, so as to better reflect the structure of
X.509 keys/certs. An OpenPGP key would still have only one email address there,
or you keep the email field, and add the array as email_s_.
----------
assignedto: marcus
messages: 1076
nosy: marc, marcus
priority: wish
status: unread
title: gpgme: use gpgme_userid_t->email instead of gpgme_userid_t->uid for x.509 email addresses.
topic: GPGME
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue217>
______________________________________________________
There is this weird convention that the DN of an x.509 cert is in
key->uids->uid, and the email address(es) in key->uids->(next->)+uid, enclosed
in <angle brackets>. However, there is an "email" field in gpgme_userid_t,
which in these cases is NULL.
A more logical place would be that email field, of course, but it should be
extended to keep a list of emails, so as to better reflect the structure of
X.509 keys/certs. An OpenPGP key would still have only one email address there,
or you keep the email field, and add the array as email_s_.
----------
assignedto: marcus
messages: 1076
nosy: marc, marcus
priority: wish
status: unread
title: gpgme: use gpgme_userid_t->email instead of gpgme_userid_t->uid for x.509 email addresses.
topic: GPGME
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue217>
______________________________________________________