1 From: Werner Koch <wk@gnupg.org>
2 Date: Mon, 3 Apr 2017 08:51:52 +0200
3 Subject: gpg: Handle critical marked 'Reason for Revocation'.
5 * g10/parse-packet.c (can_handle_critical): Add
6 SIGSUBPKT_REVOC_REASON.
9 Some software seems to mark that subpacket as criticial. Although gpg
10 has no special treatment for a revocation reasons (except for
11 --list-packets) we can accept a criticial marked anyway. There are no
12 mandatary rules specified on how to handle a revocation reason.
14 Signed-off-by: Werner Koch <wk@gnupg.org>
15 (cherry picked from commit 3f6d949011f485613bb4bd3e06a2643be79cce40)
17 g10/parse-packet.c | 1 +
18 1 file changed, 1 insertion(+)
20 diff --git a/g10/parse-packet.c b/g10/parse-packet.c
21 index 7f44ce5..bbb784a 100644
22 --- a/g10/parse-packet.c
23 +++ b/g10/parse-packet.c
24 @@ -1572,6 +1572,7 @@ can_handle_critical (const byte * buffer, size_t n, int type)
25 /* Is it enough to show the policy or keyserver? */
26 case SIGSUBPKT_POLICY:
27 case SIGSUBPKT_PREF_KS:
28 + case SIGSUBPKT_REVOC_REASON: /* At least we know about it. */