GPGME S/MIME expired flag support?

--pSm/ee5IaFm+7Fgg
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Werner,

Cc'ing you on this, just in case you are familiar with it.

In the Mutt GPGME code, in get_candidates(), the APPLICATION_PGP section=20
has code to check for revoked/expired/disabled flags:

       while (!(err =3D gpgme_op_keylist_next (ctx, &key)) )
         {
[...]

           if (key->revoked)
             flags |=3D KEYFLAG_REVOKED;
           if (key->expired)
             flags |=3D KEYFLAG_EXPIRED;
           if (key->disabled)
             flags |=3D KEYFLAG_DISABLED;

However, the APPLICATION_SMIME code in the same function is missing=20
those checks.  My theory is that, at the time, the GPGME code didn't=20
support those flags for S/MIME.  Do you happen to know if that was the=20
case, and if that has changed?

Thank you!

--=20
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

--pSm/ee5IaFm+7Fgg
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmpGEg4ACgkQre92hIAx
a9rm2hAA2VCzYABY4uZkO40PNDY/TabDgFwvLfdu2XZJdHynUlnd/4AqcCmMtEHN
QimHJBIX4+rvPbvtklI8T9WxToODAFVf3SWCKrSIqxCo/s1CoMdKoE9hTxyOCuwU
tJ5Yoq+RZE/1Jhx6M9QEkt5FVaxIGbLR/gRzMJPxetkTnU+rQ3pV+364EcyweA+Z
Bx9BmuoWbmlWkJmREqzRvWoZym7J9rdmBPRJZ6a2P+JMuZ+3MJjrbH9pUD1A8z79
68pEJf5SHLJqJjImqM0k4NzCRUdd8F3UscZz4CYa+7KjC32zH2nbnWidu2YSte6s
cvGQas1wq+BaqbyGXdbrnsKypHx9VM+Cq2D4K2/VZnyr7CkRzN3Whu90J56XhxKe
1PJYPIKjAUMEimNHxcYWcUehY7YJT56yUGSV0WlZ7/EfGbEhFM6l4700zLoBQH+g
V5iZQAnwGEGH3mWG7yMuVNZ4JFnEvd0VKXA9rm5lwiz+VZn8QKl6vtVY0J8zpNVk
UwwPigWWcRNufmLXNIwomam7h8vjgxqbCSdQy7pe4fYWZm+CLduRAuW6zUyVczGY
SX1GHOKzhfYRujsM2P6R5PE37etyp90d5PHgVA8PqCTZT7KE88jiEA8VOccPfBhy
CSibbp5xpedD65+9KqDdMvV772Zz8p3Kr+n52HwPyG++JjXxGGs=
=NK5z
-----END PGP SIGNATURE-----

--pSm/ee5IaFm+7Fgg--