[squid-users] Skype Issues

Yuri Voinov yvoinov at gmail.com
Sat Jun 25 17:34:49 UTC 2016

Hash: SHA256

25.06.2016 23:09, Amos Jeffries пишет:
> On 26/06/2016 4:32 a.m., Yuri Voinov wrote:
>> Amos, you are a wrong.
>> No Squid-4. It's unstable and not ready for production. Whenever it's
>> features.
> So some beta software has bugs therefore nobody should ever use it for
> anything. I find that to be a strange and sad view of the world.
> Care to guess why I listed it as the last option amongst several?
>  Or why 4.0.11 exists as a beta still?
> It *is* an option for the mentioned problem(s) though whatever its
>> Some time ago I have the same issue and know what happens exactly.
>> Skype initial connection site uses RC4 cipher. Which is disabled in most
>> squid's configuration.
> Your "know what happens exactly" differs from at least two other peoples
> debugging experiences with Skype.
> RC4 is on the hitlist for most of the big vendors for the past year or
> so. IIRC there were several Windows Updates to remove it and other
> broken bits from a lot of things over the past year.
> If Skype is still using RC4 it might be part of this problem.
I'm sure this is problem and this problem exists. MS do nothing to make
they sites/services more secure. BTW, MS Updates uses RC4 ciphers itself
this time. With strong siphers there is no way to setup WU via Squid.
I've spent much time to identify this problem in my setup and find
working workaround.

Another part of problem is: MS often uses it's own self-signed roots,
which is exists in Windows, but nowhere else. And which has not
cross-signed by well-known root CA's. They think it make MS services
more secure. They wrong. But we can't do anything with it. So, this is
forced us to add self-signed MS roots to our Squid's CA bundles to
>> To make it works (as by as most M$ update sites) it's require simple use
>> this cipher's suite:
>> That works for me in 5 SSL bumped setups. There is no matter which squid
>> version installed.
> Thank you. Thats another option then. I'd rate that below trying the EC
> ciphers, and above library updates.
You are welcome.

Just for information: MS has own IT infrastructure, with some strange
configured and non well-managed elements. I can't guarantee this
workaround will work everywhere or for every MS service.

When I made my research, I've seen some strange security TLS
combinations on MS sites/services. I.e., for example, RC4+ECDSA+TLSv1.2.
Or, for example, RC4+MD5+TLSv1. And some similar. Very idiotic and
potentially dangerous combinations. And - they support ignores all
requests. As usual.

To my regret, I can not order all of its users to abandon the use of
Windows. So far, in my infrastructure have machines with Windows XP.

With this nothing can be done, it is necessary only to weaken the
security - for the sake of compatibility.
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

Version: GnuPG v2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160625/5502bc69/attachment-0001.key>

More information about the squid-users mailing list