DOC: Mention that logrotate configuration needs to be adjusted if logtarget is changed (Closes: #697333)
ENH: Added login authenticator failed regexp for exim filter
Update config/filter.d/sshd.conf

Do not trigger sshd bans on pam_unix authentication failures, this will trigger on successful logins on systems that use non-pam_unix authentication (sssd, ldap, etc.).
Escape ' and " in matches tag
Merge pull request #109 from blotus/master

Escape ' and " in matches
Merge pull request #107 from opoplawski/master

sshd filter - avoid banning on pam failures since might be too early. Close gh-106

If desired to ban on pam -- enable pam-generic filter, possibly even tuning in pam-generic.local the value for caught ttys in case of more detailed control needed

Provided example was:

 Jan 18 12:47:34 host sshd[23755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.123.123.123  user=myuser
 Jan 18 12:47:34 host sshd[23755]: pam_sss(sshd:auth): authentication success; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.123.123.123 user=myuser
 Jan 18 12:47:34 host sshd[23755]: Accepted password for myuser from 123.123.123.123 port 50615 ssh2
Merge remote-tracking branch 'gh-yarikoptic/master'

* gh-yarikoptic/master:
  ENH: Added login authenticator failed regexp for exim filter
  DOC: Mention that logrotate configuration needs to be adjusted if logtarget is changed (Closes: #697333)
Initial support for --no-network option for fail2ban-testcases
BF: pyinotify - use bitwise op on masks and do not try tracking newly created directories
Remove unneeded setting of opts.no_network
Merge pull request #111 from opoplawski/nonettest

Initial support for --no-network option for fail2ban-testcases (Closes gh-110)
Merge remote-tracking branch 'gh-yarikoptic/master'

* gh-yarikoptic/master:
  BF: pyinotify - use bitwise op on masks and do not try tracking newly created directories