W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: breaking TLS (Was: Re: multiplexing -- don't do it)

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Tue, 03 Apr 2012 12:19:00 +1200
To: <ietf-http-wg@w3.org>
Message-ID: <a81e63b18bbf7ea281e1222c195ba3c2@treenet.co.nz>
On 03.04.2012 11:54, Stephen Farrell wrote:
> On 04/03/2012 12:47 AM, William Chan (ι™ˆζ™Ίζ˜Œ) wrote:
>
>>> You really mean "prevent" there? POSTing a rot13 version of the
>>> corporate secret won't work? And I thought more anti-porn policies
>>> were domain name and not content based.
>>>
>>
>> I don't mean _completely_ prevent. But help stop the 9X% case? Yeah, 
>> I
>> think that's what they're shooting for. I'm not well versed in the
>> intricacies of IT policies using these SSL MITM proxies
>
> Me neither. That's why I asked. But I'd like to know not
> just about the policy they want to (or pay to) enforce,
> but rather also about the effectiveness of their attempts
> at enforcement.
>
> S
>

IME admin are usually not that eager to do MITM on TLS. It is required 
by policy makers who just want to publish tick-box policies about the 
things they can prevent, HTTPS just being one of many policy evasions to 
be worked around. Collateral damage and accuracy is not so important as 
having the ability to be vocal about it and tick off that security 
checkbox without being caught lying.

AYJ
Received on Tuesday, 3 April 2012 00:19:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:59 GMT