Wes Gamble
2008-Sep-06 06:08 UTC
Is Rails 2.1 "protect_from_forgery" == csrf_killer plugin?
Just would like to verify: Is protect_from_forgery (in Rails 2.1) == the csrf_killer plugin from Rick Olson? Thanks, Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Frederick Cheung
2008-Sep-06 07:20 UTC
Re: Is Rails 2.1 "protect_from_forgery" == csrf_killer plugin?
On 6 Sep 2008, at 07:08, Wes Gamble <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > Just would like to verify: > > Is protect_from_forgery (in Rails 2.1) == the csrf_killer plugin from > Rick Olson? >Yup, it was merged in in rails 2.0 Fred> Thanks, > Wes > -- > Posted via http://www.ruby-forum.com/. > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Wes Gamble
2008-Sep-06 19:04 UTC
Re: Is Rails 2.1 "protect_from_forgery" == csrf_killer plugin?
Thanks, Frederick. Follow - up: Is there anything that precludes using protect_from_forgery with a DB session store? Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Frederick Cheung
2008-Sep-06 19:46 UTC
Re: Is Rails 2.1 "protect_from_forgery" == csrf_killer plugin?
On 6 Sep 2008, at 20:04, Wes Gamble wrote:> > Thanks, Frederick. > > Follow - up: Is there anything that precludes using > protect_from_forgery > with a DB session store? >nope (you do however need to pass a secret to protect_from_forgery) Fred> Wes > -- > Posted via http://www.ruby-forum.com/. > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Wes Gamble
2008-Sep-06 20:17 UTC
Re: Is Rails 2.1 "protect_from_forgery" == csrf_killer plugin?
Yeah, I just verified that. Sorry, I should have tested it first. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Maybe Matching Threads
- Upgrade to 2.0.2: InvalidAuthenticityToken error on 1st POST
- protect_from_forgery doesnt protect from forgery
- Rails3 pre and protect_from_forgery
- POST-only logic in protect_from_forgery considered harmful?
- [HELP]No :secret given to the #protect_from_forgery call