Thanks for another tip :)
God, I love this site.
Great tips.
Although it's not directly relevant to what you're talking about in this video, I'd be a little careful about telling folks they can trust sessions blindly, as those can be hijacked in a variety of ways.
See: http://en.wikipedia.org/wiki/Session_hijacking
@Robort, good point! Thanks for bringing that up.
To clarify, in the screencast I was referring to the data inside the session, not the authenticity of it. Friday I'll be posting about cross site scripting which kind of goes along with this.
Nice 'cast, as always :)
There's a blog about securing RoR applications, http://www.rorsecurity.info/ which covers a wide range of topcis (from security within rails to securing √MySQL installation). HTH :)
This is the best website on the entire planet.
Question:
Why is it that the percentage signs can not be arround the qustionmark in this statement but need to be in the second argument with the params[:query]?
Task.find(:all, :conditions=>["name LIKE ?", '%' + params[:query] + '%' ])
Thanks
Is there any reason Rails shouldn't just escape the "params" and "cookies" hashes, no matter where you put them in your code?
That would mean "escaping" the conditions hash as a whole, which might be harder than escaping each value one by one.
Seems like a good idea to me, just because stuff is easier to understand when written the insecure way - to me at least.
Thanks very much for the episodes and best wishse.
I learned a lot from here.
Here is a short informative post I wrote on SQL injections!
http://www.snailrails.com/2008/1/sql-injection
Philosophy (and it must not be supposed that this is true) may not contradict itself, but it is still possible that it may be in contradiction with the Categories, by means of analytic unity.




