Warn if config file present but unreadable
Fix up for warning/error for inaccessible config files
Update config/jail.conf

Update to use the new sogo-auth filter
Create sogo-auth.conf

Regexp works with SOGo 2.0.5 or newer, following new feature implemented here: http://www.sogo.nu/bugs/view.php?id=2229
Update config/filter.d/sogo-auth.conf

Comment line in the top altered to fit file name. My local file was named differently...
NF: allow customization configuration under corresponding .d directories (Closes gh-114)

Additional changes:
  ENH: make basedir for Config's a kwarg to the constructor
  ENH: improved analysis/reporting on presence/accessibility of config
       files.  Got carried away and forgot about existing  work done by
	   Steven Hiscocks in the gh-115 -- will merge it in the next
       commit for the fair ack of his work

Now for any X.conf configuration file we have following ways to
provide customizations

  X.local -- read after .conf (kept for backward compatibility)
  X.d/ -- directory to contain additional .conf files, sorted
               alphabetically, e.g
  X.d/01_enable.conf       - to enable the jail
  X.d/02_custom_port.conf  - to change the port

X could be a 'jail' or 'fail2ban' or any other configuration file in
fail2ban.

Mention that all files still must contain the corresponding sections
(most of the time duplicating it across all of them).
Merge remote-tracking branch 'github_kwirk_fail2ban/upstream#24' into _tent/conf_d

Merge is done with -X ours -- since I have implemented more generic handling
for config files, including now the ones under .d/ subdirectories.

* github_kwirk_fail2ban/upstream#24:
  Fix up for warning/error for inaccessible config files
  Warn if config file present but unreadable
ENH: made log messages while parsing files more informative + test for inaccessible file (Closes: gh-24)
Reincarnated removed (by mistake) test for SplitAction
Typo in default pidfile in fail2ban.conf
invalid date recognition, irregular because of sorting template list (sometimes not reproducible by fail2ban-regex, cause will be not sorted)

date in following log line (from nginx) will be wrong detected:
2012/10/11 02:37:17 [error] 18434#0: *947 user "test" was not found in "/www/...", client: 192.168.1.5, ...

sometimes it is [correct] - 2012/10/11 (%Y/%m/%d) = 1349919861.71
sometimes it is [invalid] -   12/10/11 (%d/%m/%y) = 1349915838.06
and older as now - 1800 seconds (therefore will be not found)

solution: regular expression fixed, cause date in log used always after non symbol (\W) character, so r"\d{2}/\d{2}/\d{2}" will be r"(?<!\w)\d{2}/\d{2}/\d{2}".
invalid date recognition, irregular because of sorting template list, now via setRegex
Added testcase for csocket and asyncserver
Escape ' and " in matches tag
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
RF: move exceptions used by both client and server into common/exceptions.py

this prevents importing of server while operating with client only
BF: do not rely on scripts being under /usr -- might differ eg on Fedora -- rely on import of common.version (Closes gh-112)

This is also not ideal, since if there happens to be some systemwide common.version -- we are doomed

but otherwise, we cannot keep extending comparison check to /bin, /sbin whatelse
Merge branch 'master' of git://github.com/fail2ban/fail2ban