Hi
Hmm thats strange as its openssl that is giving me the list ...
openssl ciphers 'ALL:!SSLv2:!SSLv3:@STRENGTH' plus when i don't put
anything in the ciphers option I get most (but not all of the
ciphers).
A
On 20 October 2014 12:36, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
Hi Amos,
If you need something to take a look let me know.
Thanks
Josep
-Mensaje original-
De: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] En nombre de
Amos Jeffries
Enviado el: domingo, 19 de octubre de 2014 22:32
Para: squid-users@lists.squid-cache.org
Asunto: Re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/10/2014 6:18 p.m., Tom Tom wrote:
> Hi Amos
>
> Do you have new findings? Should I open a bug for better tracking?
>
I got nothing new sorry. Yes a bug tracker would be useful to keep
track of it.
Amos
> Kind regards, Tom
>
> On Mon, Oct 13
Hi Amos
Do you have new findings? Should I open a bug for better tracking?
Kind regards,
Tom
On Mon, Oct 13, 2014 at 8:16 AM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 13/10/2014 6:26 p.m., Tom Tom wrote:
>> Hi
>>
>> Does anyone have some ideas/hints concerni
Hi.
On 19.10.2014 13:32, Victor Sudakov wrote:
>
> Hopefully I can interest our Windows admin to enable Kerberos event
> logging per KB262177.
>
> But for the present I have found an ugly workaround. In squid's keytab, I
> created another principal called 'squiduser' with the same hex key and
> kv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/10/2014 2:28 p.m., Alexander Samad wrote:
> Hi
>
> Thanks for clearing that up. so when i do a openssl ciphers and
> select the ciphers i want including the PFS enables oned, i take
> the list and try and use it in ciphers= and the list seems to
Hi
Thanks for clearing that up. so when i do a openssl ciphers and select
the ciphers i want including the PFS enables oned, i take the list and
try and use it in ciphers= and the list seems to be dissregarded and
only 1 cipher is available. atleast from online checking and with
nmap.
I have noss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2014 10:32 AM, Victor Sudakov wrote:
> Hopefully I can interest our Windows admin to enable Kerberos
> event logging per KB262177.
>
> But for the present I have found an ugly workaround. In squid's
> keytab, I created another principal calle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That is a bug. Please add to bugzilla.
Amos
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJURCItAAoJELJo5wb/XPRjtgkIAKyGuSZQnpfofxeH5VggQ/sJ
2coDiglI/rVFjO4UAaCIu3e8Vhzst7cDmWaCbY9Gre6pemlliHuX2+64TmlzPcNv
3vRxx3zqUe19w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/10/2014 8:56 p.m., Josep Borrell wrote:
> Hi,
>
> We are using a 3.4.8 squid Proxy in intercept mode via wccp. Squid
> intercepts HTTP and HTTPS via ssl_bump. All is working fine except
> that Windows Machines can't do a Windows Update. It is no
Eugene M. Zheganin wrote:
>
> On 18.10.2014 16:11, Victor Sudakov wrote:
> > I thought as much. This error seems suspicious. But why does a second
> > request not cause the same error?
> No idea.
Hopefully I can interest our Windows admin to enable Kerberos event
logging per KB262177.
But for th
11 matches
Mail list logo
