aboutsummaryrefslogtreecommitdiffstats
path: root/railties/guides/source/security.textile
diff options
context:
space:
mode:
authorVijay Dev <vijaydev.cse@gmail.com>2010-12-15 22:35:09 +0530
committerVijay Dev <vijaydev.cse@gmail.com>2010-12-15 22:35:09 +0530
commite15a55c862c98d05ff95e7fa3162ed1298ba8be7 (patch)
treec7c61073d0a0a544f26d7570b2e0ee2d455db881 /railties/guides/source/security.textile
parenta6faeffe59ce4160ddd10fd8ec8dca8d88c3a35d (diff)
downloadrails-e15a55c862c98d05ff95e7fa3162ed1298ba8be7.tar.gz
rails-e15a55c862c98d05ff95e7fa3162ed1298ba8be7.tar.bz2
rails-e15a55c862c98d05ff95e7fa3162ed1298ba8be7.zip
filter_parameter_logging is deprecated in Rails 3. Changed it to config.filter_parameters
Diffstat (limited to 'railties/guides/source/security.textile')
-rw-r--r--railties/guides/source/security.textile4
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/security.textile b/railties/guides/source/security.textile
index 528c8861d4..9963106ff3 100644
--- a/railties/guides/source/security.textile
+++ b/railties/guides/source/security.textile
@@ -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