Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-05 Thread R du Toit
Thank you for the thoughtful responses so far. I have been working in the middlebox arena for more than 20 years, and I am also concerned about the state of certain implementations. I would like to think that the TLS stack that my team and I maintain have no serious security flaws, but vulnera

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-04 Thread Hubert Kario
On Monday, 4 December 2017 19:52:59 CET Salz, Rich wrote: > > > Adam Langley posted something to this list awhile back, but I can’t > > > find it sorry. > > > > I haven't seen him mention any names either > > > I wasn’t clear. He posted that they weren’t going to post names. oh, then that

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-04 Thread Salz, Rich
> Adam Langley posted something to this list awhile back, but I can’t find it, > sorry. >I haven't seen him mention any names either I wasn’t clear. He posted that they weren’t going to post names. ___ TLS mailing list TLS@ietf.org

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-04 Thread Hubert Kario
On Saturday, 2 December 2017 17:46:24 CET Salz, Rich wrote: > ➢ I really don't understand why there is such intransparency over this > issue. Why can't we at least make clear who are the companies > responsible for this nonsense? > > Adam Langley posted something to this list awhile ba

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-03 Thread Ilari Liusvaara
On Fri, Dec 01, 2017 at 09:47:45AM -0500, R du Toit wrote: > I want to provide some feedback that might be useful to the TLS WG: > Firefox Nightly TLS 1.3 (draft 22) sessions to > tls13.crypto.mozilla.org is triggering an interesting failure in at > least one middlebox. > > Obviously the middleb

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-02 Thread Salz, Rich
➢ I really don't understand why there is such intransparency over this issue. Why can't we at least make clear who are the companies responsible for this nonsense? Adam Langley posted something to this list awhile back, but I can’t find it, sorry.

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-02 Thread Hanno Böck
On Fri, 01 Dec 2017 09:47:45 -0500 R du Toit wrote: > The middlebox in question supports TLS 1.3, but only drafts 18 > through 21. The FF Nightly ClientHello supported_versions extension > advertises support for TLS 1.2 and TLS 1.3 (draft 22), Sorry, can you please name names here? In what univ

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-01 Thread David Benjamin
On Fri, Dec 1, 2017 at 10:18 AM Eric Rescorla wrote: > On Fri, Dec 1, 2017 at 6:47 AM, R du Toit wrote: > >> I want to provide some feedback that might be useful to the TLS WG: >> Firefox Nightly TLS 1.3 (draft 22) sessions to tls13.crypto.mozilla.org >> is triggering an interesting failure in a

Re: [TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-01 Thread Eric Rescorla
On Fri, Dec 1, 2017 at 6:47 AM, R du Toit wrote: > I want to provide some feedback that might be useful to the TLS WG: > Firefox Nightly TLS 1.3 (draft 22) sessions to tls13.crypto.mozilla.org > is triggering an interesting failure in at least one middlebox. > > > > The middlebox in question supp

[TLS] TLS 1.3 draft 22 middlebox interaction

2017-12-01 Thread R du Toit
I want to provide some feedback that might be useful to the TLS WG: Firefox Nightly TLS 1.3 (draft 22) sessions to tls13.crypto.mozilla.org is triggering an interesting failure in at least one middlebox. The middlebox in question supports TLS 1.3, but only drafts 18 through 21. The FF Nigh