kommersz wrote:
My understanding was that there was a patch merged into Stunnel codeline with version 4.05 a long time ago which allows the parameters "httpsproxy_dest" and some others to be used when specifying a [https] connection in stunnel.conf.
Your understanding is not correct, but similar functionality was re-implemented from scratch.
You may consider Reading The Fine Manual at: http://stunnel.mirt.net/static/stunnel.html
The relevant part is:
protocol = proto application protocol to negotiate SSL currently supported: cifs, connect, imap, nntp, pop3, smtp
protocolAuthentication = auth_type authentication type for protocol negotiations currently supported: basic, NTLM Currently authentication type only applies to 'connect' protocol. default: basic
protocolHost = host:port destination address for protocol negotiations
protocolPassword = password password for protocol negotiations
protocolUsername = username username for protocol negotiations
Best regards, Mike