4 ms·
So now every user has to log back in again every time you upgrade your server, simply changing the signing key or when your backend gets compromised. Additiona
by rvz 7y ago
So now every user has to log back in again every time you upgrade your server, simply changing the signing key or when your backend gets compromised.
Additionally JWEs don't support forward-secrecy meaning that I can MITM and collect all JWEs passing through, find the key in your compromised backend and decrypt ALL these collected tokens.
No need to do this with JWTs since they're unencrypted by default.
- JMTQp8lwXL 7y agoYour server shouldn't be getting compromised on a regular basis. The occasional black swan event occurs, and sometimes you have no other choice.
- staticassertion 7y agoUsers get compromised though and will want to revoke sessions. But this is why you just set a time limit on your JWT, so that they can revoke and within N minutes the old sessions will die. Just keep N low.
- wcip 7y ago>Just keep N low. "Your self driving car has been compromised, but don't worry sir the attackers will relinquish control at some point in the next 30 seconds" In my view JWT are fine so long as you don't really care about whatever is they are being used for.
- deleted 7y ago[deleted]