zlacker

[return to "BlueCoat and other proxies hang up during TLS 1.3"]
1. db48x+D2[view] [source] 2017-02-28 02:06:00
>>codero+(OP)
The long-term solution is simply not to work anywhere that insists on running a MITM attack on all of your communications.
◧◩
2. stonog+64[view] [source] 2017-02-28 02:28:47
>>db48x+D2
I'm sure the students of the Montgomery County, Maryland public school system, who are affected by this problem, will take your advice into consideration when submitting resumes to other public schools.
◧◩◪
3. x1798D+F5[view] [source] 2017-02-28 02:49:33
>>stonog+64
They should lobby the school board not to do this nonsense.
◧◩◪◨
4. acdha+F6[view] [source] 2017-02-28 03:05:32
>>x1798D+F5
Think about how that conversation would go. They're driven by concerns that kids will look at porn – and remember that if they don't try to stop that, the local Fox News applicate will be running a loop 24x7 saying they're trying to force godly children to watch it – or that someone will breach a staff member's computer and steal PII, compromise the security cameras, etc.

Against that, making life hard for Chrome engineers’ aggressive upgrade campaign is pretty hard sell. “Buy a better box” perhaps but I don't see a viable argument for “don't monitor”.

◧◩◪◨⬒
5. habitu+pk[view] [source] 2017-02-28 06:05:59
>>acdha+F6
Just an FYI, local fox affiliates don't have the ideological bent of the cable station. They're often run by entirely different companies
[go to top]