SSH brute force attacks
#3
(06-19-2022, 05:27 AM)jsch Wrote: There is a risk, no doubt.
Nevertheless you could mitigate it using a firewall (don't allow ssh via interface "wwan*") and/or fail2ban.
If you need ssh only when connected w/ home WiFi, you could work with hosts.deny, see https://www.recitalsoftware.com/blogs/17...r-username . This approach leaves your ssh open when connected to another WiFi which uses the same IP range.
You could also stop the ssh service when not required.

Thanks, I will evaluate those solution, howto know if I have been hacked that way?
  Reply


Messages In This Thread
SSH brute force attacks - by user641 - 06-19-2022, 04:53 AM
RE: SSH brute force attacks - by jsch - 06-19-2022, 05:27 AM
RE: SSH brute force attacks - by user641 - 06-19-2022, 06:22 AM
RE: SSH brute force attacks - by Zebulon Walton - 06-19-2022, 06:39 AM
RE: SSH brute force attacks - by wibble - 06-20-2022, 01:42 AM
RE: SSH brute force attacks - by user641 - 06-20-2022, 03:42 AM
RE: SSH brute force attacks - by Zebulon Walton - 06-20-2022, 06:03 AM
RE: SSH brute force attacks - by wibble - 06-20-2022, 06:38 AM
RE: SSH brute force attacks - by user641 - 06-20-2022, 07:14 AM
RE: SSH brute force attacks - by wibble - 06-20-2022, 08:33 AM
RE: SSH brute force attacks - by user641 - 06-20-2022, 08:48 AM
RE: SSH brute force attacks - by bitnick - 06-21-2022, 11:38 AM
RE: SSH brute force attacks - by user641 - 06-21-2022, 04:45 PM
RE: SSH brute force attacks - by RTP - 06-23-2022, 12:49 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)