wrong csrf cookie name?

[eluser]coolgeek[/eluser]
Yes, thanks. It's a known bug.

The problem was that I had rolled back to 2.0.1 in my dev environment, but had not yet done so in my prod environment (which isn't actually in production yet)