New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix forward compatibility of keys, SKESKs, and detached/cleartext signatures and ECDH #1656
Conversation
05f0564
to
dd006d1
Compare
try { | ||
offset += this.s2k.read(bytes.subarray(offset, bytes.length)); | ||
} catch (err) { | ||
throw new UnsupportedError('Unsupported or invalid S2K'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change the type of the errors in s2k.read
instead? (And add a try/catch around the enums.read
there, I guess)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we just have to merge this after #1658
dd006d1
to
225ec7d
Compare
368f0e4
to
b638edd
Compare
…e packet versions Relevant for forward compatibility when verifying detached signatures that include e.g. v4 and v6 packets
…re packet versions
These messages should still be decrypt-able if they include at least one supported ESK packet.
Keys with such subkeys should still be usable, as long as they have a supported primary key.
b638edd
to
32caf41
Compare
Relevant for forward compatibility when:
UnparseablePacket
to properly deal with key blocks that include malformed/unsupported packets #1522 .