06.12.2017 16:57, Matus UHLAR - fantomas пишет:
>>> On Wed, Dec 6, 2017 at 7:01 AM, Jason Haar wrote:
To reiterate Alex, "yes you can".
Squid supports "proxy over TLS" as well as the old/default "proxy
over TCP"
- you use the https_port option
...but getting bro
On Wed, Dec 6, 2017 at 7:01 AM, Jason Haar wrote:
To reiterate Alex, "yes you can".
Squid supports "proxy over TLS" as well as the old/default "proxy over TCP"
- you use the https_port option
...but getting browsers to support it is challenging. The best way would be
to create a WPAD file that
On 06/12/17 21:32, Mathieu Peltier wrote:
On Wed, Dec 6, 2017 at 7:01 AM, Jason Haar wrote:
To reiterate Alex, "yes you can".
Squid supports "proxy over TLS" as well as the old/default "proxy over TCP"
- you use the https_port option
...but getting browsers to support it is challenging. The be
On Wed, Dec 6, 2017 at 7:01 AM, Jason Haar wrote:
> To reiterate Alex, "yes you can".
>
> Squid supports "proxy over TLS" as well as the old/default "proxy over TCP"
> - you use the https_port option
>
> ...but getting browsers to support it is challenging. The best way would be
> to create a WPAD
To reiterate Alex, "yes you can".
Squid supports "proxy over TLS" as well as the old/default "proxy over TCP"
- you use the https_port option
...but getting browsers to support it is challenging. The best way would be
to create a WPAD file that tells browsers to use "HTTPS" instead of
"PROXY". Th
On 12/04/2017 10:05 AM, Amos Jeffries wrote:
> On 05/12/17 04:42, Colle Christophe wrote:
>> I am currently using Squid for internet access. Currently, "basic"
>> authentication on an LDAP directory is configured to identify users.
>> The problem is that the password is sent in clear (base64) and I
On 05/12/17 04:42, Colle Christophe wrote:
Hello!
I am currently using Squid for internet access. Currently, "basic"
authentication on an LDAP directory is configured to identify users. The
problem is that the password is sent in clear (base64) and I am looking
for a solution to secure it.
Hi Anthony,
Thank you for your answer.
That this only secures the traffic Squid<->LDAP Server, not browsers<->Squid.
Is there a solution to secure communication between the browser and the proxy?
Chris.
Le 04/12/17 16:49, Antony Stone a écrit :
>
> On Monday 04 December 2017 at 16:42:30
On Monday 04 December 2017 at 17:06:03, Amos Jeffries wrote:
> On 05/12/17 04:49, Antony Stone wrote:
> > On Monday 04 December 2017 at 16:42:30, Colle Christophe wrote:
> >> Is there a solution to secure the "basic" authentication of squid? (with
> >> an SSL certificate for example).
> >
> > htt
On 05/12/17 04:49, Antony Stone wrote:
On Monday 04 December 2017 at 16:42:30, Colle Christophe wrote:
Is there a solution to secure the "basic" authentication of squid? (with an
SSL certificate for example).
https://wiki.squid-cache.org/ConfigExamples/Authenticate/Ldap section
"SSL/TLS_adjus
On Monday 04 December 2017 at 16:42:30, Colle Christophe wrote:
> Is there a solution to secure the "basic" authentication of squid? (with an
> SSL certificate for example).
https://wiki.squid-cache.org/ConfigExamples/Authenticate/Ldap section
"SSL/TLS_adjustments"?
Antony.
--
"Linux is goin
Hello!
I am currently using Squid for internet access. Currently, "basic"
authentication on an LDAP directory is configured to identify users. The
problem is that the password is sent in clear (base64) and I am looking for a
solution to secure it.
I tested the "Digest" mode, but the result is
12 matches
Mail list logo