除非你做到网站完全静态化,否则,有用户输入的地方就有SQL注入的可能,我们应该注意到这些潜在的危险
在 防SQL注入方面,ruby和php相比要逊色一些,php提供了多个过滤函数,直接调用即可,但ruby需要自己去写正则;
当然,rails在与数据库交互时,参数化查询方面做得很到位,举例如下:
一:
错误写法:Department.find :first,:conditions=>["id = message.department_id"]
正确写法:Department.find :first,:conditions=>["id = ?", message.department_id]
二:
错误写法:
content = params[:content]
sql_content = "content like content "
sql_fdate = "and date(created_at) >= '#{date}'"
sql_tdate = "and date(created_at) <= '#{date}'"
Suggestion.paginate :all,:conditions=>[" #{sql_content} #{sql_fdate} #{sql_tdate}],:page=> params[:page], :per_page=> Per_Page,:order => "id DESC"
正确的写法:
content = params[:content]
sql_content = "content like ? "
sql_fdate = "and date(created_at) >= '#{date}'"
sql_tdate = "and date(created_at) <= '#{date}'"
Suggestion.paginate :all,:conditions=>[" #{sql_content} #{sql_fdate} #{sql_tdate} ","%#{content}%"],:page=> params[:page], :per_page=> Per_Page,:order => "id DESC"