Regards to using proxies, I believe this is covered in the draft. But at a high level, most enterprises have tried this approach. It can work in some situations, but in most cases there are utilization, performance and management issues that prevent this solution from being effective or affordable. Not to mention the introduction of manifold new potential points of failure.
From: Timothy Jackson [mailto:tjack...@mobileiron.com] Sent: Friday, July 7, 2017 11:19 PM To: Ackermann, Michael <mackerm...@bcbsm.com>; Watson Ladd <watsonbl...@gmail.com>; Christian Huitema <huit...@huitema.net> Cc: tls@ietf.org Subject: Re: [TLS] draft-green-tls-static-dh-in-tls13-01 As an earlier poster asked, what advantage does this approach have over TLS-inspecting proxies? Every IPS/IDS/next gen firewall with which I am familiar is able to terminate at TLS connection, inspect/copy/filter, and then encrypt on a new TLS sessions. For high performance customers, the SSL accelerators can be sandwiched around the filter so all the crypto is done in hardware. The ways to prevent TLS inspection are cert pinning and client cert auth. If this is only within one's data center, then those features can be disabled if necessary, no? What use case am I missing that can't be achieved better by other means than static keys? Thanks, Tim Sent from Email+ secured by MobileIron ________________________________ From: "Ackermann, Michael" <mackerm...@bcbsm.com<mailto:mackerm...@bcbsm.com>> Date: Friday, July 7, 2017 at 7:06:55 PM To: "Watson Ladd" <watsonbl...@gmail.com<mailto:watsonbl...@gmail.com>>, "Christian Huitema" <huit...@huitema.net<mailto:huit...@huitema.net>> Cc: "tls@ietf.org<mailto:tls@ietf.org>" <tls@ietf.org<mailto:tls@ietf.org>> Subject: Re: [TLS] draft-green-tls-static-dh-in-tls13-01 Converting all session traffic to clear text is not a viable alternative for ANY enterprises or industries that I am aware of. In particular those in financial sectors. Security policies, legislation and in many cases just good practice would not allow for this. We are compelled by these factors to encrypt all data in motion. But we still need to manage our applications, networks, servers and clients. Hence the need to decrypt traffic as outlined in this draft. -----Original Message----- From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Watson Ladd Sent: Friday, July 7, 2017 9:40 PM To: Christian Huitema <huit...@huitema.net<mailto:huit...@huitema.net>> Cc: tls@ietf.org<mailto:tls@ietf.org> Subject: Re: [TLS] draft-green-tls-static-dh-in-tls13-01 On Fri, Jul 7, 2017 at 6:10 PM, Christian Huitema <huit...@huitema.net<mailto:huit...@huitema.net>> wrote: > > > On 7/7/2017 2:54 PM, Russ Housley wrote: >> Stephen: >> ... >>> And also: I'm sorry to have to say it, but I consider that attempted >>> weasel wording around the clear intent of 2804. The clear and real >>> effect if your wiretapping proposal were standardised by the IETF >>> would be that we'd be standardising ways in which TLS servers can be >>> compelled into breaking TLS - it'd be a standard wiretapping API >>> that'd be insisted upon in many places and would mean significantly >>> degrading TLS (only *the* most important security protocol we >>> maintain) and the community's perception of the IETF. It's all a >>> shockingly bad idea. >> I clearly disagree. Otherwise, I would not have put any work into the draft. > Russ, > > What are the specific mechanisms that would allow this technique to be > used where you intend it, i.e. within a data center, and not where > Stephen fears it would be, i.e., on the broad Internet? For example, > what mechanism could a client use to guarantee that this sort of > "static DH" intercept could NOT be used against them? The server can send the plaintext to whomever it likes. This is the solution enterprises can use today. Nothing can stop that from happening. So I don't see why static DH is a) so essentially necessary and b) so controversial. >From a technical point I prefer using DH shares derived from ServerRandom as this avoids certain bugs I've been known to exploit from time to time. > > -- > Christian Huitema > > > _______________________________________________ > TLS mailing list > TLS@ietf.org<mailto:TLS@ietf.org> > https://www.ietf.org/mailman/listinfo/tls -- "Man is born free, but everywhere he is in chains". --Rousseau. _______________________________________________ TLS mailing list TLS@ietf.org<mailto:TLS@ietf.org> https://www.ietf.org/mailman/listinfo/tls The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies. Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association. _______________________________________________ TLS mailing list TLS@ietf.org<mailto:TLS@ietf.org> https://www.ietf.org/mailman/listinfo/tls The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies. Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
