💾 Archived View for rawtext.club › ~sloum › geminilist › 007450.gmi captured on 2021-11-30 at 19:37:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Anna “CyberTailor” cyber at sysrq.in
Wed Oct 27 08:14:51 BST 2021
- - - - - - - - - - - - - - - - - - -
On 2021-10-27 08:40, Alex Schroeder wrote:
I kept working on this page on how to deal with bots, and I'd be happy
to add more ideas, or refine the existing sections. If anybody is
interested in how to get fail2ban to work with their server, I'd be
happy to add pages explaining how to do this if you provide me with a
log file snippet, for example.
=
//transjovian.org:1965/gemini/page/Dealing%20with%20bots
Feel free to copy and use elsewhere.
Feel free to mail me directly with comments.
Good job!
### Banning IP numbers is problematic
It’s true. Perhaps there’s a shared server at that IP number. One of
the users on that server writes a misbehaving bot and all are
punished. If you are concerned about that, your server needs to move
the dynamic content behind a client certificate requirement. There is
no other way to identify particular users using Gemini.
I'm concerned about that, so I have Tor exit nodes explicitly ignoredfrom blocking. That's what I have in my jail.d files (except for sshd):
ignorecommand = /bin/grep <ip> /etc/tor/torbulkexitlist
/etc/tor/torbulkexitlist is updated daily by a cronjob fromhttps://check.torproject.org/torbulkexitlist