Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace obsolete captcha with Google captcha #822

Closed
benya opened this issue Jan 26, 2021 · 3 comments · Fixed by #1067
Closed

Replace obsolete captcha with Google captcha #822

benya opened this issue Jan 26, 2021 · 3 comments · Fixed by #1067

Comments

@benya
Copy link

benya commented Jan 26, 2021

Captcha which is now practically useless in our time. It is better to replace it with Google or any other analogue

@jcogs-design
Copy link
Contributor

If we are going to do this, it would be even more functional to see if the "snaptcha" addon can be integrated with EE6 - and so side-step the need for catpcha's completely!

https://putyourlightson.com/plugins/snaptcha-ee

@blue-dreamer
Copy link

Whatever Captcha system is used it should be privacy focused and not leak data to 3rd parties outside the EE ecosystem. Many countries now have privacy laws we must adhere to so we shouldn't be forced to use products such as Google's captcha or similar.

A "Snaptcha" type system would be perfect, it would be 1st party code and respects privacy.

@benya
Copy link
Author

benya commented Jan 30, 2021

Not without reason it should be Google captcha.

You just need to improve this captcha as it is.

Bots can easily bypass it.

For example, you can replace it with the hidden field "honeypot"

We say the submission will “fail”, but that’s not exactly true. On the front end it will appear that the form was submitted successfully. However, nothing will get saved and no emails will be sent. This is the key to tricking bots into believing everything went smoothly.

This option works for me on another CMS, and it catches spam many times better than the captcha from EE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants