stunnel TODO


High priority features I'm going to support (sponsorship appreciated)
* Provide 64-bit Windows builds (besides 32-bit builds).
* Request elevated UAC privileges before editing stunnel.conf
  on Microsoft's Windows Vista, Windows Server 2008, and later.
* Indirect CRL support (RFC 3280, section 5).
* Separate GUI process running as current user on Windows.
* Separate control process running as root user on Unix.
* Features depending on using MSVC for OpenSSL build:
  - Support for CryptoAPI certificates and private keys with CAPI engine.
* Service-level logging configuration (separate verbosity and destination).

Low priority features I'm going to support (sponsorship appreciated)
* SOCKS 4 protocol support.
  http://archive.socks.permeo.com/protocol/socks4.protocol
* Key renegotiation (re-handshake) for long connections.
* Logging to NT EventLog on Windows.
* Internationalization of logged messages (i18n).
* Generic scripting engine instead or static protocol.c.

Features I prefer *not* to support (waiting for a wealthy sponsor)
* Protocol support *after* SSL is negotiated:
  - Support for adding X-Forwarded-For to HTTP request headers.
  - Support for adding X-Forwarded-For to SMTP email headers.
* Additional certificate checks (including wildcard comparison) based on
  CN and X509v3 Subject Alternative Name.
* Set processes title that appear on the ps(1) and top(1) commands.

