0
@@ -71,10 +71,14 @@
0
   #     end
0
   #   end
0
   # 
0
-  # The +authenticate_unsafely+ method inserts the parameters directly into the query and is thus susceptible to SQL-injection
0
-  # attacks if the +user_name+ and +password+ parameters come directly from a HTTP request. The +authenticate_safely+ method, on
0
-  # the other hand, will sanitize the +user_name+ and +password+ before inserting them in the query, which will ensure that
0
+  # The <tt>authenticate_unsafely</tt> method inserts the parameters directly into the query and is thus susceptible to SQL-injection
0
+  # attacks if the <tt>user_name</tt> and +password+ parameters come directly from a HTTP request. The <tt>authenticate_safely</tt> method, 
0
+  # on the other hand, will sanitize the <tt>user_name</tt> and +password+ before inserting them in the query, which will ensure that
0
   # an attacker can't escape the query and fake the login (or worse).
0
+  #
0
+  # Beware, that the approach used in <tt>authenticate_unsafely</tt> is basically just a wrapped call to sprintf. This means that you
0
+  # still have to quote when using %s or use %d instead. So find_first([ "firm_id = %s", firm_id ]) is _not_ safe while both
0
+  # find_first([ "firm_id = '%s'", firm_id ]) and find_first([ "firm_id = %d", firm_id ]) are.
0
   # 
0
   # == Overwriting default accessors
0
   #