Skip to content

Commit

Permalink
filter_parameter_logging is deprecated in Rails 3. Changed it to conf…
Browse files Browse the repository at this point in the history
…ig.filter_parameters
  • Loading branch information
vijaydev authored and fxn committed Dec 15, 2010
1 parent dfecb3f commit 34ed401
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions railties/guides/source/security.textile
Original file line number Diff line number Diff line change
Expand Up @@ -524,10 +524,10 @@ h4. Logging

-- _Tell Rails not to put passwords in the log files._

By default, Rails logs all requests being made to the web application. But log files can be a huge security issue, as they may contain login credentials, credit card numbers et cetera. When designing a web application security concept, you should also think about what will happen if an attacker got (full) access to the web server. Encrypting secrets and passwords in the database will be quite useless, if the log files list them in clear text. You can _(highlight)filter certain request parameters from your log files_ by the filter_parameter_logging method in a controller. These parameters will be marked [FILTERED] in the log.
By default, Rails logs all requests being made to the web application. But log files can be a huge security issue, as they may contain login credentials, credit card numbers et cetera. When designing a web application security concept, you should also think about what will happen if an attacker got (full) access to the web server. Encrypting secrets and passwords in the database will be quite useless, if the log files list them in clear text. You can _(highlight)filter certain request parameters from your log files_ by appending them to config.filter_parameters in the application configuration. These parameters will be marked [FILTERED] in the log.

<ruby>
filter_parameter_logging :password
config.filter_parameters << :password
</ruby>

h4. Good Passwords
Expand Down

0 comments on commit 34ed401

Please sign in to comment.