Have captcha and email enabled before the creation of this account (email: `kanaloa.javeon@findours.com`).
Already had before without captcha a similar surrogacy ad.
~~Should send me a notification on new gitea user.~~ Done.
Can view to quickly see such new users: https://gitea.lemnoslife.com/admin/users
Let say image captcha is too easy, let's move to hcaptcha and could set Passing Threshold to Difficult if spam continues.
Let's try to avoid banning a single IP, as it's quite easy to circumvent that.
https://github.com/go-gitea/gitea/issues/6350
Let say `image` captcha is too easy, let's move to hcaptcha and could set `Passing Threshold` to `Difficult` if spam continues.
Let's try to avoid banning a single IP, as it's quite easy to circumvent that.
Could also consider disabling registration (DISABLE_REGISTRATION) but instead put a message to contact me to get an account, or could use REGISTER_MANUAL_CONFIRM but then may be spammed with account requests.
Should deepen DEFAULT_USER_IS_RESTRICTED.
```
access.log:45.77.165.103 - - [23/May/2023:14:44:52 +0200] "GET /Benjamin_Loison/Synchronous_reactive_systems/issues/9 HTTP/2.0" 200 17912 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36"
access.log:45.77.165.103 - - [23/May/2023:14:44:52 +0200] "GET /Benjamin_Loison/Synchronous_reactive_systems/issues/9/content-history/overview?_csrf=gG0trb3QdzNiIO-UuzXHJ2tuTcg6MTY4NDg0NTgzNjQzNzYxMjk3MQ HTTP/2.0" 200 184 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36"
```
`samuelmegan@yopmail.com`
I increased hCatpcha difficulty to difficult.
Could then try reCaptcha.
https://docs.gitea.com/next/help/faq#adjusting-your-server-for-publicprivate-use
Could consider `EMAIL_DOMAIN_BLACKLIST`.
Could also consider disabling registration (`DISABLE_REGISTRATION`) but instead put a message to contact me to get an account, or could use `REGISTER_MANUAL_CONFIRM` but then may be spammed with account requests.
Should deepen `DEFAULT_USER_IS_RESTRICTED`.
As a result I added communication means to my profile for people really interested in having an account, would be nice to change the registration message error, but it doesn't seem possible currently.
Got spammed again, so disabled registrations.
As a result I added communication means to [my profile](https://gitea.lemnoslife.com/Benjamin_Loison) for people really interested in having an account, would be nice to change the registration message error, but [it doesn't seem possible currently](https://github.com/go-gitea/gitea/blob/a43ea22479334ef3ac05fb8784223d45846b71a3/templates/user/auth/signup_inner.tmpl#L15-L17).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Have captcha and email enabled before the creation of this account (email:
kanaloa.javeon@findours.com).Already had before without captcha a similar surrogacy ad.
Should send me a notification on new gitea user.Done.Can view to quickly see such new users: https://gitea.lemnoslife.com/admin/users
Can we get their IPs? To potentially drop their traffic if they always use the same IP, as it seems to be done by a single entity.
Another case with email
josephpaul@yopmail.com.Can we also use a inter-instances connected captcha? For instance hCaptcha backend might detect a spammer sending one message per instance.
Thanks to:
in
/var/log/nginx/it brought up the IP209.95.53.223at the same moment the post was created.So thanks to:
find these logs in
access.log.1:As the first line shows, it seems to be the same person every time.
Email:
danielgary@yopmail.commaxxon.cayse@fullangle.org



https://github.com/go-gitea/gitea/issues/6350
Let say
imagecaptcha is too easy, let's move to hcaptcha and could setPassing ThresholdtoDifficultif spam continues.Let's try to avoid banning a single IP, as it's quite easy to circumvent that.
samuelmegan@yopmail.comI increased hCatpcha difficulty to difficult.
Could then try reCaptcha.
https://docs.gitea.com/next/help/faq#adjusting-your-server-for-publicprivate-use
Could consider
EMAIL_DOMAIN_BLACKLIST.Could also consider disabling registration (
DISABLE_REGISTRATION) but instead put a message to contact me to get an account, or could useREGISTER_MANUAL_CONFIRMbut then may be spammed with account requests.Should deepen
DEFAULT_USER_IS_RESTRICTED.Got spammed again, so disabled registrations.
As a result I added communication means to my profile for people really interested in having an account, would be nice to change the registration message error, but it doesn't seem possible currently.