diff options
| author | Werner Koch <[email protected]> | 2011-04-25 21:56:47 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 2011-04-25 21:59:25 +0000 |
| commit | 5da12674eaae11969b22e6f80e4957217ad406d6 (patch) | |
| tree | 1ae8b482a2c2cdef4cb24055d6d15c99224b5b1d /g10/trustdb.c | |
| parent | Add OPTION:cache-ttl-opt-preset to gpg-agent. (diff) | |
| download | gnupg-5da12674eaae11969b22e6f80e4957217ad406d6.tar.gz gnupg-5da12674eaae11969b22e6f80e4957217ad406d6.zip | |
Fix regression in gpg's mail address parsing.
Since 2009-12-08 gpg was not able to find email addresses indicated
by a leading '<'. This happened when I merged the user id
classification code of gpgsm and gpg.
Diffstat (limited to '')
| -rw-r--r-- | g10/trustdb.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/g10/trustdb.c b/g10/trustdb.c index c8964323e..c6ff6922d 100644 --- a/g10/trustdb.c +++ b/g10/trustdb.c @@ -217,7 +217,7 @@ register_trusted_key( const char *string ) gpg_error_t err; KEYDB_SEARCH_DESC desc; - err = classify_user_id (string, &desc); + err = classify_user_id (string, &desc, 1); if (err || desc.mode != KEYDB_SEARCH_MODE_LONG_KID ) { log_error(_("`%s' is not a valid long keyID\n"), string ); |