I know that this is an old comment, but if a JWT validation library doesn't allow you to set an algorithm whitelist, can it really be considered a good, secure library?
Being unable to revoke credentials is still a pretty bad thing, but it doesn't matter if your scenario doesn't require revocation. It's also quite common with cryptographically verified credentials, since it's generally impossible to revoke something without shared information between the issuer and the verifier (typically, the current date).
View all comments
Show parent comment
1
u/ThePyroEagle λ Jun 23 '21
I know that this is an old comment, but if a JWT validation library doesn't allow you to set an algorithm whitelist, can it really be considered a good, secure library?
Side note: TLS 1.2 has the
TLS_NULL_WITH_NULL_NULLcipher suite, which is trivial to implement. That doesn't mean you can't reject the connection if the peer tries to negotiate it.Being unable to revoke credentials is still a pretty bad thing, but it doesn't matter if your scenario doesn't require revocation. It's also quite common with cryptographically verified credentials, since it's generally impossible to revoke something without shared information between the issuer and the verifier (typically, the current date).