unknown critical bit

[Werner Koch]

> Looking at can_handle_critical in parse-packet.c, we see that
> SIGSUBPKT_REVOC_REASON is not considered to be supported with respect
> to the critical bit.

That is the first time such an issue was reported.  I am a bit taken
aback to learn that this implementation did not test against gpg.
Anyway, I just committed

    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.

to master to go into 2.1.20.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: </pipermail/attachments/20170403/deba737a/attachment.sig>