Removed check which was refusing to check for extensions in SSL 3.0

Sniproxy contained a check that would refuse to parse an SSL 3.0 packet
for extensions. This check was wrong as SSL 3.0 explicitly allows for
additional data in the end of a Client Hello (see RFC6101 last paragraph of
5.6.1.2). In fact most browsers set SSL 3.0 as the record packet version
irrespectively of the TLS version they support (which is advertized inside
the Client Hello).

Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>
Separated daemonize from dropping permissions.

Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
If system provides a daemon(0,0) use it.

That makes sniproxy follow system conventions (e.g., in linux
daemon() does not need to fork twice, something that systemd
relies on).

Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
remove any old pidfile

Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
print usage when cannot open config file

Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Merge pull request #59 from nmav/usage-fix

print usage when cannot open config file
Merge pull request #60 from nmav/simplify-startup

Simplify startup
Merge pull request #61 from nmav/fix-ssl3

Removed check which was refusing to check for extensions in SSL 3.0
Merge remote-tracking branch 'github/master' into nonblocking-connect