Re^4: Is your web application really secure? ("CSRF")

in reply to Re^3: Is your web application really secure? ("CSRF")
in thread Is your web application really secure? ("CSRF")

it all depends on how secure you want the application. if you're doing online-banking i think even you are glad that usually you have a timeout of 10 minutes and you can't let windows open and expect them to work an hour later =)

Comment on Re^4: Is your web application really secure? ("CSRF")

Replies are listed 'Best First'.
Re^5: Is your web application really secure? ("CSRF") by betterworld (Curate) on Apr 03, 2007 at 15:33 UTC
Quite right. Using the approach that I described above, you can set the expiration timeout to 10 minutes and nobody will be able to waste you money online while you're absent. But the point is, that when you come back, you only need to login in one browser tab, and all the other tabs work again. Regardless of the cookie expiration timeout. Nevertheless, if the computer is in a room where many people wander about, you should lock the screen or something like that.	[reply]

Replies are listed 'Best First'.

Re^5: Is your web application really secure? ("CSRF")
by betterworld (Curate) on Apr 03, 2007 at 15:33 UTC

one

Nevertheless, if the computer is in a room where many people wander about, you should lock the screen or something like that.

[reply]

In Section Meditations