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
I'm doing a bit of software spelunking/archaeology, and I'd like to be able to parse old PGP signatures and access their signer information (specifically, Key IDs).
This looks wrong to me: rather than pass-ing, this should probably either raise an exception or (longer-term) handler whatever older/legacy packet type appears in these older signatures. That way, the PGPSignature object itself is never constructed in an invalid/inaccessible state.
I'm happy to make the changes for the quick fix (raising an exception); the more detailed fix should probably be done by someone who understands PGP better 🙂
The text was updated successfully, but these errors were encountered:
Hi there! Thanks for maintaining this library.
I'm doing a bit of software spelunking/archaeology, and I'd like to be able to parse old PGP signatures and access their signer information (specifically, Key IDs).
For example, a signature like this:
When I try to load that with
PGPSignature.from_blob(...)
, I don't get an exception:However, as soon as I try to access
s
(even just itsrepr
), I get anAttributeError
:I did a quick check, and it looks like this is coming from the following packet check:
PGPy/pgpy/pgp.py
Lines 585 to 592 in 30a7571
This looks wrong to me: rather than
pass
-ing, this should probably either raise an exception or (longer-term) handler whatever older/legacy packet type appears in these older signatures. That way, thePGPSignature
object itself is never constructed in an invalid/inaccessible state.I'm happy to make the changes for the quick fix (raising an exception); the more detailed fix should probably be done by someone who understands PGP better 🙂
The text was updated successfully, but these errors were encountered: