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: | Re: Cookies as the second factor |
|---|---|
| Date: | Tue, 18 Jul 2006 22:06:37 -0400 |
I'm not saying it's a good idea, just that it can done very easily. Ronans posting made it appear technically impossible.
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
--
Thank you, Darren Bounds
------------------------------------------------------------------------- Sponsored by: Watchfire
https://www.watchfire.com/securearea/appscancamp.aspx?id=70150000000CYkc -------------------------------------------------------------------------
| Previous by Date: | Re: Cookies as the second factor, mikeiscool |
|---|---|
| Next by Date: | Re: Disable SSL v2 ciphers on IIS 5.0, Eoin Miller |
| Previous by Thread: | Re: Cookies as the second factor, mikeiscool |
| Next by Thread: | Re: Cookies as the second factor, Nick Owen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |