* keylist.c (set_mainkey_capability): Handle 'd' and 'D' used

since gpg 1.3 to denote disabled keys.
This commit is contained in:
Werner Koch 2003-01-06 21:06:23 +00:00
parent 8e65687b46
commit 3552416199
3 changed files with 18 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2003-01-06 Werner Koch <wk@gnupg.org>
* keylist.c (set_mainkey_capability): Handle 'd' and 'D' used
since gpg 1.3 to denote disabled keys.
2003-01-06 Marcus Brinkmann <marcus@g10code.de>
* data-mem.c: Include <string.h>.

View File

@ -43,7 +43,7 @@ extern "C" {
AM_PATH_GPGME macro) check that this header matches the installed
library. Warning: Do not edit the next line. configure will do
that for you! */
#define GPGME_VERSION "0.4.0"
#define GPGME_VERSION "0.4.1"
/* The opaque data types used by GPGME. */

View File

@ -141,6 +141,8 @@ set_mainkey_trust_info (GpgmeKey key, const char *src)
break;
case 'd':
/* Note that gpg 1.3 won't print that anymore but only uses
the capabilities field. */
key->keys.flags.disabled = 1;
break;
@ -241,6 +243,16 @@ set_mainkey_capability (GpgmeKey key, const char *src)
key->keys.flags.can_certify = 1;
break;
case 'd':
case 'D':
/* Note, that this flag is also set using the key validity
field for backward compatibility with gpg 1.2. We use d
and D, so that a future gpg version will be able to
disable certain subkeys. Currently it is expected that
gpg sets this for the primary key. */
key->keys.flags.disabled = 1;
break;
case 'E':
key->gloflags.can_encrypt = 1;
break;