| 26 Feb 2025 |
 hexa | also a valid choice | 20:24:05 |
| hexa | so what happens is that due to too many connection requests ssh also sometimes drops my connect attempts | 20:25:54 |
| hexa | mildly annoying 🙂 | 20:26:06 |
| hexa |
sshd[1969703]: error: beginning MaxStartups throttling
| 20:26:57 |
| hexa | due to that | 20:26:58 |
 dgrig | All the things you mentioned help however. I personally change the ssh port, enable fail2ban and for a lot of hosts don't have ssh enabled over the internet since wireguard works good enough for me. Other people I know enable ssh only over tor hidden services, but I don't trust tor starting fast enough after a restart /shrug | 20:27:01 |
 magic_rb | I only allow ssh over wireguard period | 20:28:33 |
| dgrig | (waiting for a new circuit after a restart can be a bit annoying if you're trying to ssh right after a restart in my opinion) | 20:28:36 |
 Scrumplex | Another way to reduce ssh bot noise is to limit sshd to listen on IPv6 only | 20:50:50 |
 Fernando Rodrigues | In reply to @magic_rb:matrix.redalder.org
I only allow ssh over wireguard period ssh over wireguard is so nice | 21:36:06 |
| hexa | yeah, much nicer than just using ssh over internet | 21:38:07 |
| hexa | * yeah, much nicer than just using ssh over internet \s | 21:38:09 |
