Skip to content
This repository has been archived by the owner on Jun 13, 2018. It is now read-only.

Commit

Permalink
document fail2ban filters in security.md
Browse files Browse the repository at this point in the history
  • Loading branch information
JoshData committed Aug 8, 2016
1 parent fc5cc97 commit 81b5af6
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions security.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,16 @@ The [setup guide video](https://mailinabox.email/) explains how to verify the ho

If DNSSEC is enabled at the box's domain name's registrar, the SSHFP record that the box automatically puts into DNS can also be used to verify the host key fingerprint by setting `VerifyHostKeyDNS yes` in your `ssh/.config` file or by logging in with `ssh -o VerifyHostKeyDNS=yes`. ([source](management/dns_update.py))

### Brute-force attack mitigation

`fail2ban` provides some protection from brute-force login attacks (repeated logins that guess account passwords) by blocking offending IP addresses at the network level.

The following services are protected: SSH, IMAP (dovecot), SMTP submission (postfix), webmail (roundcube), ownCloud/CalDAV/CardDAV (over HTTP), and the Mail-in-a-Box control panel & munin (over HTTP).

Some other services running on the box may be missing fail2ban filters.

`fail2ban` only blocks IPv4 addresses, however. If the box has a public IPv6 address, it is not protected from these attacks.

Outbound Mail
-------------

Expand Down

0 comments on commit 81b5af6

Please sign in to comment.