He talks about "cross site" but as you see it's actually worse than that. A solution of this problem would be by implementing the logout as a POST form.
A safer, more reliable way to guard against CSRF is to make destructive action URLs impossible for an attacker to create. For example, require a parameter which is a big number based on something in the "victim's" session. A salted, hash of the logged in user's session_id works pretty well.
Mouse over the signout link about to see how I've done it.
Discussion (3)
Chris Shiflett wrote an interesting article about this problem: http://shiflett.org/articles/cross-site-request-forgeries
He talks about "cross site" but as you see it's actually worse than that. A solution of this problem would be by implementing the logout as a POST form.
A safer, more reliable way to guard against CSRF is to make destructive action URLs impossible for an attacker to create. For example, require a parameter which is a big number based on something in the "victim's" session. A salted, hash of the logged in user's session_id works pretty well.
Mouse over the signout link about to see how I've done it.
It didn't work, sorry...