Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-566

Replacement for CAPTCHA functionality

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.1.0
    • Fix Version/s: None
    • Component/s: Security
    • Labels:
      None
    • External issue URL:
    • Additional information:
      Hide

      Small correction:

      for correct simultaneous form submissions, two hidden fields should be dynamically added, one with name like "verification_key" and another with name like "verification_value", also this pair is stored on server in session array called like "verification_pairs" with "verification_key" as key and "verification_value" as value. Then on submission we take session array element with passed key and compare passed value to stored one.

      Sure, also we verify that both key and value have been passed, and passed key exists in session array.

      Show
      Small correction: for correct simultaneous form submissions, two hidden fields should be dynamically added, one with name like "verification_key" and another with name like "verification_value", also this pair is stored on server in session array called like "verification_pairs" with "verification_key" as key and "verification_value" as value. Then on submission we take session array element with passed key and compare passed value to stored one. Sure, also we verify that both key and value have been passed, and passed key exists in session array.
    • Change Log Message:
      Created replacement for Security Image functionality
    • Story Points:
      2
    • External issue ID:
      715
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      Today most popular approach is to place captcha code on form to verify, that humans (not search engines) are submitting site forms. More dirty captcha image is, more chances are spider/bot won't be able to recognize it. On the other hand it makes form submitting uncomfortable for users. Also captcha is used only on forms, when user is not logged in.

      Here is approach, that is not using captcha, but still provides same level of protection:

      1. after page with form is loaded, then send ajax request to server
      2. in ajax response send random name and random value + save both to session
      3. when ajax response is received, then dynamically add hidden field with received name and value
      4. when form is submitted, then check, that submitted value matches generated one from session

      We are generating random hidden field name to allow same form to be submitted from different tabs of same browser, when we have same user session. Because of spiders don't execute page javascript this approach can work.

        Attachments

          Issue Links

          mentioned in

          Page Loading...

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dmitry Dmitry Andrejev [Intechnic]
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: