The new crate took the position of validating keys lazily. Our current ed25519 code in the cryptography crate, on the other hand, validates public keys proactively.
We should have a means of providing compatibility, either by changing the default behavior of the crate, or by adding in a path towards proactive validation.
We do still want a path towards fast batch validation of keys though, in either case.
c.f. #4699 for some work towards this. Here the behavior was changed to match the existing code.
The new crate took the position of validating keys lazily. Our current ed25519 code in the cryptography crate, on the other hand, validates public keys proactively.
We should have a means of providing compatibility, either by changing the default behavior of the crate, or by adding in a path towards proactive validation.
We do still want a path towards fast batch validation of keys though, in either case.
c.f. #4699 for some work towards this. Here the behavior was changed to match the existing code.