On 10/03/2016 2:35 p.m., Eliezer Croitoru wrote:
> On 09/03/2016 21:31, Jason Haar wrote:
>> Or use socat. I have used it to allow ancient SSLv3-only clients to
>> communicate with TLS-only servers.
>>
>> Jason
>
> Would it be possible to put haproxy as a SSL termination proxy and pass
> the TCP r
On 09/03/2016 21:31, Jason Haar wrote:
Or use socat. I have used it to allow ancient SSLv3-only clients to
communicate with TLS-only servers.
Jason
Would it be possible to put haproxy as a SSL termination proxy and pass
the TCP request to squid? which will results in a similar situation to
s
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
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
> > provi
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
On Thu, 2015-10-01 at 13:26 +0200, Job wrote:
> Hello,
>
> by reading the 3.5 Squid verson "Peek and splice" features:
> http://wiki.squid-cache.org/Features/SslPeekAndSplice
>
> i would like to ask you two questions, please:
>
> 1. in this implementations, i have to install the selfmade Certif
01.10.15 17:26, Job пишет:
Hello,
by reading the 3.5 Squid verson "Peek and splice" features:
http://wiki.squid-cache.org/Features/SslPeekAndSplice
i would like to ask you two questions, please:
1. in this implementations, i have to install the selfmade Certification
Authority as for SSL Bu
