Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | best practices |
|---|---|
| Date: | Thu, 14 Sep 2006 23:31:21 -0300 |
Hi,
Normally in web application, when a user end his session, not logging out, but simply closing the browser, the session token stay valid until the session timed out, and so it's potentially reusable.
In my opinion it's recommendable that some kind of a mechanism is implemented for invalidate the session token when user close the browser, for example, with a client side javascript code using the onunload event to invalidate the session token. But I haven't found a best practices or any other discussion about this problem.
Best Regards,
Matteo Nava
------------------------------------------------------------------------- Sponsored by: Watchfire
https://www.watchfire.com/securearea/whitepapers.aspx?id=701500000008Vmm --------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Hardcoded Database IP in ASP, Darryl Stevens |
|---|---|
| Next by Date: | Re: best practices, Rick Zhong |
| Previous by Thread: | Hardcoded Database IP in ASP, Darryl Stevens |
| Next by Thread: | Re: best practices, Rick Zhong |
| Indexes: | [Date] [Thread] [Top] [All Lists] |