You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ifnotself.key_id: # don't corrupt the key id with 'gpg-exit nnnnn'
As far as I can tell, the value that is associated with the FAILURE key is not a key-id, so should never be used to set the key_id.
So whilst the PR fixed the immediate issue, the key_id could still end up with an invalid value.
I don't know whether the UNEXPECTED message value can be a key_id.
The text was updated successfully, but these errors were encountered:
PR #180 prevented FAILURE messages from overwriting the key_id:
python-gnupg/gnupg.py
Line 337 in 0dab090
As far as I can tell, the value that is associated with the FAILURE key is not a key-id, so should never be used to set the key_id.
So whilst the PR fixed the immediate issue, the key_id could still end up with an invalid value.
I don't know whether the UNEXPECTED message value can be a key_id.
The text was updated successfully, but these errors were encountered: