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 <wk@gnupg.org>
(cherry picked from commit 3f6d949011f485613bb4bd3e06a2643be79cce40)

Gbp-Pq: Name 0059-gpg-Handle-critical-marked-Reason-for-Revocation.patch

diff --git a/g10/parse-packet.c b/g10/parse-packet.c
index 7f44ce532c782270f4a9a93aa1a25ebb4c34ca2d..bbb784a908c6d996767dff8aeded48eb97efcf2d 100644 (file)
--- a/g10/parse-packet.c
+++ b/g10/parse-packet.c
@@ -1572,6 +1572,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: