4 ms·
This is not limited to AWS/rackspace... Here's from my home PC: $ uptime 22:09:07 up 30 days, 12:19, 2 users, load average: 0,17, 0,09, 0,07 $ sudo fail2
by wazoox 13y ago
This is not limited to AWS/rackspace... Here's from my home PC:
$ uptime
22:09:07 up 30 days, 12:19, 2 users, load average: 0,17, 0,09, 0,07
$ sudo fail2ban-client status ssh-iptables
Password:
Status for the jail: ssh-iptables
|- filter
| |- File list: /var/log/messages
| |- Currently failed: 1
| `- Total failed: 1757
`- action
|- Currently banned: 0
| `- IP list:
`- Total banned: 242
1757 attempts from 242 IP address in the past 30 days...
- akx 13y agoMy home NAS is also exposed to the internet. up 298 days, 20:42, 1 user, load average: 0.00, 0.01, 0.05 "zgrep ssh auth.log* | grep -i failed" has no traces of any intrusion attempts whatsoever, just me not being able to type. The distinction is, though, that the SSHd on that box is running on a non-standard port (220)... so that certainly makes a difference.