3 ms·
> the others are just "bad code works badly" problems Software should be hard to misuse. If you have a library intended for universal usage, and the library us
by marcosdumay 4y ago
> the others are just "bad code works badly" problems
Software should be hard to misuse. If you have a library intended for universal usage, and the library users have to remember to add some code every time they call it, then it's a bad library.
If you have an specification intended for universal usage, and the implementers have to remember to always do 3 operations together, than it's a bad specification.
- kreetx 4y agoRight, but rm -fr / is also easy to write, but is pretty bad code. JWTs and statelessness have their uses, building in refreshing is not that difficult (if it's not built in already), and using "none" well, just don't use that.
- marcosdumay 4y agoThere are alternatives that won't accept "none" or broken encryption algorithms, and that won't allow you to access the token data without verifying its authenticity. JWT is just a bad standard all around.
- 0x457 4y agoMany issues of JWT are actually issues on library for nodejs to work with JWTs and partially the language: trick server to use public key as secret to validate JWT, trick server to use none. JWT itself is also poor by having things like "none" at all. Which means in every valid place to use JWT, you should really be using PASETO.