diff options
| author | Werner Koch <[email protected]> | 2017-04-03 06:51:52 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 2017-04-03 06:51:52 +0000 |
| commit | 3f6d949011f485613bb4bd3e06a2643be79cce40 (patch) | |
| tree | 04dc45ee658946e774bec942390eb9101ea99847 /g10/parse-packet.c | |
| parent | agent: Use OCB for key protection with --enable-extended-key-format. (diff) | |
| download | gnupg-3f6d949011f485613bb4bd3e06a2643be79cce40.tar.gz gnupg-3f6d949011f485613bb4bd3e06a2643be79cce40.zip | |
gpg: Handle critical marked 'Reason for Revocation'.
* g10/parse-packet.c (can_handle_critical): Add
SIGSUBPKT_REVOC_REASON.
--
Some software seems to mark that subpacket as criticial. Although gpg
has no special treatment for a revocation reasons (except for
--list-packets) we can accept a criticial marked anyway. There are no
mandatary rules specified on how to handle a revocation reason.
Signed-off-by: Werner Koch <[email protected]>
Diffstat (limited to 'g10/parse-packet.c')
| -rw-r--r-- | g10/parse-packet.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/g10/parse-packet.c b/g10/parse-packet.c index ffed95628..2be984993 100644 --- a/g10/parse-packet.c +++ b/g10/parse-packet.c @@ -1643,6 +1643,7 @@ can_handle_critical (const byte * buffer, size_t n, int type) /* Is it enough to show the policy or keyserver? */ case SIGSUBPKT_POLICY: case SIGSUBPKT_PREF_KS: + case SIGSUBPKT_REVOC_REASON: /* At least we know about it. */ return 1; default: |