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
The same is true if the certificate contains a bad signature, a
signature with an odd signature type, a signature with an unknown
version, a key with an unknown version, or a packet with an
unknown tag. See the last five lines of the following test for
test vectors:
This is problematic if a certificate gets slightly mangled (some
version of SKS apparently did that), and dismissing certificates
with unknown packet versions prevents a smooth upgrade path to
newer packet versions.
In contrast, OpenPGP.js handles these cases gracefully.
The text was updated successfully, but these errors were encountered:
When a certificate contains an unbound subkey, GopenPGP refuses
to encrypt for the certificate's bound subkey:
The same is true if the certificate contains a bad signature, a
signature with an odd signature type, a signature with an unknown
version, a key with an unknown version, or a packet with an
unknown tag. See the last five lines of the following test for
test vectors:
https://tests.sequoia-pgp.org/#Perturbed_certificates
This is problematic if a certificate gets slightly mangled (some
version of SKS apparently did that), and dismissing certificates
with unknown packet versions prevents a smooth upgrade path to
newer packet versions.
In contrast, OpenPGP.js handles these cases gracefully.
The text was updated successfully, but these errors were encountered: