If a service section is not presented in the configuration then stunnel will
always start anyway. This ends in a crash loop because the configuration is not
valid.
Checking in "uci" mode if a service section is presented and only then
start the stunnel service will solve this issue.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>

Do not send a SIGHUP on reload configuration let procd restart the
service with stop/start. This is saver.

Add uci generated stunnel file to procd "file" attribute to
reload/restart the stunnel service.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>

Add an enabled option for the service section, so you could keep your
configuration in place without apply this section on startup or service reload.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>

Add uci config support.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>

From: Michael Haas <haas@computerlinguist.org>

* init script no longer creates certificates (consider client mode as use
  case)
* patches/010_fix_getnameinfo.patch: Fix getnameinfo signature
* patches/011_disable_ssp_linking.patch: Disable -fstack-protector as it
  is not always available in OpenWRT
* old patches (in oldpackages) no longer necessary
* remove libwrap dependency
* remove libpthread dependency
* respect CONFIG_IPV6
* init script uses procd
* sample stunnel.conf runs in client mode - prevents start failure,
  does not require cert

Possible enhancement: automatically generate certificate as done in
uhttpd. However, as client mode is a possible use case, I'd rather not.
Additionally, stunnel may use several certs with user-defined locations
and we can't easily set a cert location via command-line args.

The package is based on
https://sites.google.com/site/twisteroidambassador/openwrt/stunnel

Signed-off-by: Michael Haas <haas@computerlinguist.org>