[git] GnuPG - branch, master, updated. gnupg-2.1.19-106-g3f6d949

[by Werner Koch]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GNU Privacy Guard".

The branch, master has been updated
       via  3f6d949011f485613bb4bd3e06a2643be79cce40 (commit)
      from  d24375271b97e45deaeb1ef0a8434c64066ba2e8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
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>

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:

-----------------------------------------------------------------------

Summary of changes:
 g10/parse-packet.c | 1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
The GNU Privacy Guard
http://git.gnupg.org