Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har...
by jaywalk on Thursday April 16, 2020 @12:38PM
(#22891122)
It's funny that they say it's "not suitable" when it's really just pure laziness. It takes two seconds to create a secret key and use the HS256 algorithm to generate and verify a signature.
Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har...
by kelnos on Thursday April 16, 2020 @03:46PM
(#22892769)
Creating a key is easy; storing it securely and giving access to only the parts of your system that need it takes a bit more work.
Of course, if you trust your network and the parties involved well enough that you'd be fine with unencrypted and unauthenticated data, I guess it doesn't matter if you just check the key into a git repo somewhere... but then you're potentially normalizing bad practices, even if in that particular instance it might be ok.
Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har...
by different_sort on Thursday April 16, 2020 @01:54PM
(#22891829)
"trusted server"
FTFA:
> The JWT standard supports insecure JWT algorithms for scenarios where encryption and a signature are not suitable, such as trusted server-to-server communication. In these scenarios, the none algorithm is specified in the JWT header. The none alg type should never be used for untrusted user-supplied tokens.