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

Protect form with captcha #19

Open
Aszusz opened this issue Dec 21, 2021 · 4 comments
Open

Protect form with captcha #19

Aszusz opened this issue Dec 21, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@Aszusz
Copy link
Collaborator

Aszusz commented Dec 21, 2021

Protect feedback form with captcha to prevent spamming on email address

@Aszusz Aszusz added the enhancement New feature or request label Dec 21, 2021
@Aszusz Aszusz self-assigned this Dec 21, 2021
@piotrzarzycki21
Copy link
Collaborator

@Aszusz Unfortunately I'm still seeing spam coming out from our website. Last two emails come on 31/12/2021 and 01/01/2022

@Aszusz
Copy link
Collaborator Author

Aszusz commented Jan 11, 2022

Unfortunately I'm still seeing spam coming out from our website. Last two emails come on 31/12/2021 and 01/01/2022

This proves the current form we use (from Formspree) doesn't provide adequate protection.

I tried to use GetResponse's form instead but I don't see anywhere an option to redirect a form's content to an email address. It looks like GetResponse can only store feedback form's content in its own mailing list which is insufficient for our needs.

@Aszusz
Copy link
Collaborator Author

Aszusz commented Jan 11, 2022

@JoelProminic
After a brief discussion with @piotrzarzycki21 we decided the best course of action will probably be to use our own implementation of Google ReCaptcha v3. @JoelProminic would you be willing to spend some time and provide a backend agent that can validate ReCaptcha requests and send emails to our support system?

@JoelProminic
Copy link
Collaborator

By my understanding:

Unfortunately, we can't submit directly from moonshine-ide.com to my agents at rest-swf.prominic.net or x.prominic.net because of CORS restrictions. Some workarounds:

  • You could submit the request from the moonshine-ide.com server instead
  • We could setup a new subdomain for the requests from Moonshine, but this seems like overkill.
  • We could implement one of the more complicated CORS solutions we discussed for the Prominic website, but these are not trivial to change.

If we can get past this problem, we'll need to generate separate reCAPTCHA keys for moonshine-ide.com. Otherwise, the agent should be pretty trivial, since I can reuse existing code and libraries.

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

No branches or pull requests

3 participants