[Pkg-gnupg-commit] [gnupg2] 106/124: gpg: Handle critical marked 'Reason for Revocation'.

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch experimental
in repository gnupg2.

commit 3f6d949011f485613bb4bd3e06a2643be79cce40
Author: Werner Koch <wk at gnupg.org>
Date:   Mon Apr 3 08:51:52 2017 +0200

    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 at gnupg.org>
---
 g10/parse-packet.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/g10/parse-packet.c b/g10/parse-packet.c
index ffed956..2be9849 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:

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gnupg2.git