6 ms·
This exact issue occurred with TLS 1.2 back when BlueCoat only understood 1.1/1.0. Good grief! From David Benjamin's final comment: Note these issues are alwa
by jessaustin 10y ago
This exact issue occurred with TLS 1.2 back when BlueCoat only understood 1.1/1.0.
Good grief! From David Benjamin's final comment:
Note these issues are always bugs in the middlebox products. TLS version negotiation is backwards compatible, so a correctly-implemented TLS-terminating proxy should not require changes to work in a TLS-1.3-capable ecosystem. It can simply speak TLS 1.2 at both client <-> proxy and proxy <-> server TLS connections. That these products broke is an indication of defects in their TLS implementations.
It's understandable that I've never heard of BlueCoat: clearly this product's success is based more on selling to executives than on quality, and it has been some time since I worked in an organization that had executives to sell to.
- jacquesm 10y agoIt sounds like it might be a worthwhile effort to reverse engineer one of those.
- AlyssaRowan 10y agoReverse-engineer? A middlebox? Which holds trusted secret keys and which, in its normal unremarkable operation, intercepts, parses, reconstructs, decrypts, re-encrypts, forwards, and optionally logs both confidential and attacker-controlled traffic? And is also known to be used for nationwide bulk internet censorship by regimes often called 'oppressive'? Why, doesn't it just. Please consider, very carefully, the ethics and equities issues one might face with any interesting findings here.
- lmm 10y agoWhat's true is true - better to know it than stick our heads in the sand. If these boxes have vulnerabilities (who am I kidding, they do parsing, they're probably implemented in C "for performance", of course they have vulnerabilities), we are better off for knowing about them than not.
- AlyssaRowan 10y agoBut what of the equities issue - what to do with that knowledge, once discovered? Might it depend on who "we" are? My point is that actually helping this particular vendor, for example, may not be everyone's cup of tea.
- jacquesm 10y agoYes, good point. One might aim to 'help' them into an early grave whilst actually helping them to strengthen their product.
- nl 10y agoBluecoat is extremely widely used in some fields. They were in the news a while back when it was discovered that Syria (before the civil war) was censoring their internet access using Bluecoat devices (allegedly unauthorized by Bluecoat)[1] [1] https://en.wikipedia.org/wiki/Blue_Coat_Systems#Use_by_repressive_regimes https://en.wikipedia.org/wiki/Blue_Coat_Systems#Use_by_repre...
- pjmlp 10y agoThey have many costumers on the Fortune 500 portfolio that make sure the workers only visit the web sites they should and also IT get to know when they misbehave. Quite a pain to work in such environments.
- semi-extrinsic 10y agoThere was a paper posted on HN a few weeks back by some pretty serious security researchers on the security risks of SSL MITM boxes. https://jhalderm.com/pub/papers/interception-ndss17.pdf https://jhalderm.com/pub/papers/interception-ndss17.pdf How do you fix this when you're naught but a humble employee? Well, a friend of mine worked at a fairly large tech company where a salesguy for these boxes had convinced the CTO they had to have them. Every tech-person "on the floor" hated the idea, so before the boxes were installed they conspired on their free time to write some scripts that ran lots of legitimate HTTPS traffic, effectively DDOSing the boxes and bringing the company's internet to a crawl for the day, like Google would take ten seconds to open. Then obviously everyone (including the non-tech people) started calling the IT helpdesk complaining that the internet was broken. MITM box salesguy then had to come up with a revised solution, costing 20x more than his first offer, and that was the end of that. If you already are suffering under MITM boxes, a similar strategy with a slow ramp-up in traffic might work.
- adrianN 10y agoIt might backfire and your company forbids HTTPS "so that employees can't disclose company secrets without IT having traceability".
- ptaipale 10y agoThey can't, really. So much of the Web has fortunately moved to HTTPS that then they should just forget about Web access.
- trome 10y agoUhh, what do you do for sites that don't offer HTTP? Many sites force a 301 redirect when hit on HTTP, and won't downgrade.
- adrianN 10y agoOpen a ticket with IT?
- 10y ago
- skywhopper 10y agoThe entire use case of BlueCoat and the like is to satisfy executives' desire to spy on all usage of their network. It's certainly not to benefit the users who are stuck behind it, to increase their security, or to give them a better Internet experience.
- 794CD01 10y agoFuck the users. If users had their way, they'd have all the local administrator privileges they wanted so that they could download malware to their heart's content. From a non-IT perspective, they would also be free to download porn, potentially child porn, which is a crime to merely possess, and exfiltrate terabytes of company secrets.