Our great sponsors
-
ssh-audit
SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc) (by jtesta)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Match Address 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 PasswordAuthentication yes ```` You may audit your SSH service by https://github.com/jtesta/ssh-audit
It does, but it defaults to nftables from (I think) Ubuntu 21 and onwards. So when you're running fail2ban in a docker container, it run an iptables command to block the IP. However, it errors out because nftables is default in Ubuntu 19 onwards (only for new installs). See https://github.com/crazy-max/docker-fail2ban down the page. You can replace the defaults, but I do not want to mess with my docker box at this point!
Related posts
- fail2ban for reverse proxy inside docker
- Is putting fail2ban/ufw in front of Docker+Traefik v2 necessary? How do Docker+Traefik handle the same need?
- Possible to redirect container logs to file
- Docker compose, orchestrating and automating services
- Blue-Green Deployment on Single Machines Starting from Scratch, Using Your Dockerfiles: Examples in PHP, Java, and Node.js