aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/security.md
diff options
context:
space:
mode:
authorDaniel Colson <danieljamescolson@gmail.com>2018-01-28 17:44:01 -0500
committerDaniel Colson <danieljamescolson@gmail.com>2018-01-28 17:44:01 -0500
commit600c4138dd778f4e5633846b5b68a89dbb77193d (patch)
tree4ec304b38342921354a5d19e2aee1d2fdc29f8ac /guides/source/security.md
parent2f9549d4f46ca1f9cc437d4f89bd8df405e28dbd (diff)
downloadrails-600c4138dd778f4e5633846b5b68a89dbb77193d.tar.gz
rails-600c4138dd778f4e5633846b5b68a89dbb77193d.tar.bz2
rails-600c4138dd778f4e5633846b5b68a89dbb77193d.zip
Remove joke in security guide [ci skip]
I think this is a joke, although not a great one. It's mildly unprofessional, so I think we should get rid of it.
Diffstat (limited to 'guides/source/security.md')
-rw-r--r--guides/source/security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/security.md b/guides/source/security.md
index ab5a5a7a31..724d952d4e 100644
--- a/guides/source/security.md
+++ b/guides/source/security.md
@@ -551,7 +551,7 @@ Here are some ideas how to hide honeypot fields by JavaScript and/or CSS:
* make the elements very small or color them the same as the background of the page
* leave the fields displayed, but tell humans to leave them blank
-The most simple negative CAPTCHA is one hidden honeypot field. On the server side, you will check the value of the field: If it contains any text, it must be a bot. Then, you can either ignore the post or return a positive result, but not saving the post to the database. This way the bot will be satisfied and moves on. You can do this with annoying users, too.
+The most simple negative CAPTCHA is one hidden honeypot field. On the server side, you will check the value of the field: If it contains any text, it must be a bot. Then, you can either ignore the post or return a positive result, but not saving the post to the database. This way the bot will be satisfied and moves on.
You can find more sophisticated negative CAPTCHAs in Ned Batchelder's [blog post](http://nedbatchelder.com/text/stopbots.html):