Hi,
If your network is set up to pass all traffic through a proxy, without a gateway set on clients, you won't be able to use anything that the proxy server isn't configured for.
Have in mind, anyway, that Stunnel doesn't act as a proxy and the purpose isn't to connect dinamically to different endpoints. The software, if there is some with that purpose, behind the other endpoint of Stunnel is the one that does it. Stunnel just creates a secure tunnel between two peers.
Regards.
On Tue, Apr 03, 2018 at 06:52:06PM +0200, Javier wrote:
Hi,
If your network is set up to pass all traffic through a proxy, without a gateway set on clients, you won't be able to use anything that the proxy server isn't configured for.
Have in mind, anyway, that Stunnel doesn't act as a proxy and the purpose isn't to connect dinamically to different endpoints. The software, if there is some with that purpose, behind the other endpoint of Stunnel is the one that does it. Stunnel just creates a secure tunnel between two peers.
I believe that the original poster is talking about using stunnel's support for an HTTP(S) proxy using the CONNECT protocol (look for the "protocol" keyword in the configuration manual).
However, it does indeed seem that proxy authentication has not been implemented yet; it is in the to-do list - "Add user-defined headers to CONNECT proxy requests" is one of the items listed in the source distribution's TODO file. You'd have to ask Dr. Trojnara about the chances of it being implemented soon, although it may be under similar conditions as the rest of the items in this list, as stated at the start of the TODO file.
Best regards, Peter
Why would he use the protocol option, when is for HTTP when... ?
to overcome a proxy server which allows only http and https
Or I totally misunderstood, but my guess was that he was trying to use other kind of service through the proxy server.
I guess, now, that I totally misunderstood.
No clue, then.