My question is: how practical would it be to use a 1TB RSA key for average users? I assume that the size of cipher text would be somewhat depended on secret size. The storage space and network bandwidth is not free.
I don't see any valid arguments in the post. The issues raised are either mis-implementation or misuse of JWT. All I am getting is "JWT can be misused in such such way that makes your application vulnerable. And neither…
Yep. Revocation is tricky with JWT, but it's not that bad. The expectation should be reduce in database io, not getting rid of it entirely. Overall you could issue tokens with short lifespan, say 5 minutes. And having…
Which is more possible? A bug or they just underestimated the volume of traffic that could be caused by ATA in real life?
My question is: how practical would it be to use a 1TB RSA key for average users? I assume that the size of cipher text would be somewhat depended on secret size. The storage space and network bandwidth is not free.
I don't see any valid arguments in the post. The issues raised are either mis-implementation or misuse of JWT. All I am getting is "JWT can be misused in such such way that makes your application vulnerable. And neither…
Yep. Revocation is tricky with JWT, but it's not that bad. The expectation should be reduce in database io, not getting rid of it entirely. Overall you could issue tokens with short lifespan, say 5 minutes. And having…
Which is more possible? A bug or they just underestimated the volume of traffic that could be caused by ATA in real life?