New submission from Marc Mutz <marc@klaralvdalens-datakonsult.se>:
Currently, every application needs to include it's own DN parsing code. We,
e.g. use a slightly C++-ified version of what is presumably the original code
in gpgsm. Since that is not exactly trivial code, it would be best to not
require the gpgme user to write it :)
A new field
struct dn_pair * dn;
in gpgme_key_t (since there's only ever one of them, like the issuer_serial and
chain_id), or, if it must be, in gpgme_userid_t.
After all, you also provide a parsed-down version of OpenPGP uids:
(name,comment,email).
----------
assignedto: marcus
messages: 1077
nosy: marc, marcus
priority: wish
status: unread
title: gpgme: include a struct dn_pair * dn; in either gpgme_userid_t or gpgme_key_t
topic: GPGME
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue218>
______________________________________________________
Currently, every application needs to include it's own DN parsing code. We,
e.g. use a slightly C++-ified version of what is presumably the original code
in gpgsm. Since that is not exactly trivial code, it would be best to not
require the gpgme user to write it :)
A new field
struct dn_pair * dn;
in gpgme_key_t (since there's only ever one of them, like the issuer_serial and
chain_id), or, if it must be, in gpgme_userid_t.
After all, you also provide a parsed-down version of OpenPGP uids:
(name,comment,email).
----------
assignedto: marcus
messages: 1077
nosy: marc, marcus
priority: wish
status: unread
title: gpgme: include a struct dn_pair * dn; in either gpgme_userid_t or gpgme_key_t
topic: GPGME
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue218>
______________________________________________________