Or use socat. I have used it to allow ancient SSLv3-only clients to communicate with TLS-only servers.
Jason
On Thu, Mar 10, 2016 at 12:28 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:
On 9/03/2016 6:53 p.m., Howard Kranther wrote:
> Hello, I am investigating the use of squid as a client side proxy to
> provide TLS 1.2 support for a VOIP application using SIP over TCP.The
> application would use TCP or TLS 1.0 to communicate with squid, which
> would bump either of those to TLS 1.2 to communicate with a phone
> system.The application uses a commercial SIP stack so adding an HTTP
> CONNECT message to the start of a SIP session and processing the
> response is problematic.
Squid is an HTTP proxy. CONNECT is the only way non-HTTP compatible
protocols can be delivered over HTTP.
You need to go looking for a SOCKS proxy.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 481 8171
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
