06-19-2022, 05:27 AM
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.
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.