summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2016-09-01 18:55:20 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2016-09-01 19:24:26 +0200
commit6dc85f53d92b9763a1509a6472227c54bc70b01d (patch)
treea8d9839e9d50652051dd328bf1e5a89ca9a24d0b /COPYING
parentf9c2f3e972313b14c4408950d86dc2dba49f8c7c (diff)
support long keyid and fingerprint in gpgv's GOODSIG
In gpgv1 GOODSIG (and the other messages of status-fd) are documented as sending the long keyid. In gpgv2 it is documented to be either long keyid or the fingerprint. At the moment it is still the long keyid, but the documentation hints at the possibility of changing this. We care about this for Signed-By support as we detect this way if the right fingerprint has signed this file (or not). The check itself is done via VALIDSIG which always is a fingerprint, but there must also be a GOODSIG (as expired sigs are valid, too) found to be accepted which wouldn't be found in the fingerprint-case and the signature hence refused.
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions