WebApp Sec mailing list archives
Re: Cookies as the second factor
From: mikeiscool <michaelslists () gmail com>
Date: Wed, 19 Jul 2006 11:28:03 +1000
On 7/19/06, Darren Bounds <dbounds () gmail com> wrote:
There's no reason a cookie couldn't be generated client-side. I could easily have a client-side application generate a 'secure', one-time use token, populate a cookie and then use that value as one part of a multi-factor authentication scheme.
except that if your 'client' is compromised you are stuffed. two factor should work even in a client-compromised situation. -- mic ------------------------------------------------------------------------- Sponsored by: WatchfireAppScan 6.5 is now available! New features for Web Services Testing, Advanced Automated Capabilities for Penetration Testers, PCI Compliance Reporting, Token Analysis, Authentication testing, Automated JavaScript execution and much more. Download a Free Trial of AppScan today!
https://www.watchfire.com/securearea/appscancamp.aspx?id=70150000000CYkc -------------------------------------------------------------------------
Current thread:
- Re: Cookies as the second factor, (continued)
- Re: Cookies as the second factor Rogan Dawes (Jul 18)
- RE: Cookies as the second factor Matt Fisher (Jul 18)
- Re: Cookies as the second factor Andrew van der Stock (Jul 18)
- RE: Cookies as the second factor Randy Ollett (Jul 18)
- RE: Cookies as the second factor Andrew Chong (Jul 18)
- RE: Cookies as the second factor Ken Kousky (Jul 18)
- Re: Cookies as the second factor Ryan Barnett (Jul 18)
- RE: Cookies as the second factor Jeff Robertson (Jul 18)
- RE: Cookies as the second factor Matt Fisher (Jul 18)
- Re: Cookies as the second factor mikeiscool (Jul 18)
- Re: Cookies as the second factor Darren Bounds (Jul 18)
- RE: Cookies as the second factor Jeff Robertson (Jul 20)
- Re: Cookies as the second factor Robert Hajime Lanning (Jul 20)
- Re: Cookies as the second factor Peter Watkins (Jul 21)
- RE: Cookies as the second factor Arian J. Evans (Jul 25)