3 ms·
Is that a problem though? Does your threat model include clients that correctly send logout requests when they're supposed to but don't delete cookies when they
by remram 6y ago
Is that a problem though? Does your threat model include clients that correctly send logout requests when they're supposed to but don't delete cookies when they're told?
- colinclerk 6y agoYour application should certainly have some resolution to an account being hacked or a session token being stolen. No expiry and no denylist means an attacker can cause problems until you patch your code.
- SigmundA 6y agoNever trust the client, ever.
- remram 6y agoIf that's how you feel, don't trust them to logout when they walk away. Make those sessions short-lived and ask for the password again whenever they do something remotely sensitive.
- jfgiogktkt 6y agoYou logout on a public computer, the next user undeletes the cookie (which is just a row in a profile SQLite database).
- remram 6y agoCouldn't the previous user have rigged the app to not send the logout request, or way more plausibly installed a keylogger to get your password, which allows them to log in again at will? I'm not disagreeing with you, it just seems to only cover a very specific type of attack, if someone else can mess with software. And of course if they can't it is unnecessary.