News for hackers. Stuff that matters.
Re:What Craigslist Did Right: User Management Without Userna... by scriby on Wednesday February 15, 2012 @05:30PM (#3596441)
This looks wide open to csrf attacks.

Another site can post a form on behalf of a user automatically, and the cookies for job poacher will be sent. Meaning that a malicious site can take actions on behalf of a logged in user.

Perhaps their solution is more complicated than they let on, but I doubt it given it's "20 lines of code".

Re:What Craigslist Did Right: User Management Without Userna... by cheald on Wednesday February 15, 2012 @07:03PM (#3596765)
Rails has CSRF protections baked in; unless you explicitly turn it off, non-GET requests require a CSRF token associated with the user session to complete successfully.
Re:What Craigslist Did Right: User Management Without Userna... by scriby on Wednesday February 15, 2012 @09:25PM (#3597104)
That makes sense. I've been doing node js too long where you have to do this stuff by hand :0
Re:What Craigslist Did Right: User Management Without Userna... by joevandyk on Thursday February 16, 2012 @07:15PM (#3601370)
This is why you check for tokens in the form that correspond to the current user's session. Rails does this for you automatically.
Re:What Craigslist Did Right: User Management Without Userna... by zaroth on Wednesday February 15, 2012 @07:04PM (#3596767)
that has nothing to do with using a password or not to authenticate. anti-forgery tokens are the answer to csrf.