Brian Eaton wrote: > If somebody knows of CSRF protection techniques that can > survive an XSS hole in the application, I'd love to hear about them.
How about requireing password (again)?
That's a start. I see three issues.
1) Javascript malware injected through the XSS hole could watch the keystrokes. 2) Javascript malware could change the message on the confirmation page, so that the user doesn't realize what he is confirming. 3) It bugs people. It's just bad from a usability perspective.
Regards, Brian