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. bgc+Q6[view] [source] 2017-02-28 03:07:55
>>x1798D+F5
The Board doesn't have a choice, under CIPA[0], content filtering is a requirement for the FCC's E-Rate program[1] in which the government pays some of the cost of the school's internet connection.

[0]https://www.fcc.gov/consumers/guides/childrens-internet-prot...

[1]https://www.fcc.gov/general/universal-service-program-school...

◧◩◪◨⬒
5. fulafe+S9[view] [source] 2017-02-28 03:47:33
>>bgc+Q6
Of course they have a choice. It's not very princinpled to sell your children's online privacy in exchange for some "grant" money going to an oppressive-dictatorship supporting company like BlueCoat.

(Also it's possible can do server address based blocking without MITM)

[go to top]