Re: [TLS] Malformed Finished handling

2018-07-09 Thread Hubert Kario
On Wednesday, 4 July 2018 15:46:04 CEST Salz, Rich wrote: > >if the interpretation of "I know this _message_ _length_ is wrong > >because of > >some other values I negotiated before, so I'll send illegal_parameter" > >was correct, then overflow_error, decrypt_error and probably fe

Re: [TLS] Malformed Finished handling

2018-07-09 Thread Hubert Kario
On Wednesday, 4 July 2018 18:54:10 CEST Eric Rescorla wrote: > On Wed, Jul 4, 2018 at 6:36 AM, Hubert Kario wrote: > > On Wednesday, 4 July 2018 15:00:18 CEST Eric Rescorla wrote: > > > I think it's a close call, because the length is sort of external to the > > > language. > > > > which language

Re: [TLS] Malformed Finished handling

2018-07-09 Thread Hubert Kario
On Thursday, 5 July 2018 02:06:45 CEST Martin Thomson wrote: > On Wed, Jul 4, 2018 at 7:55 PM Hubert Kario wrote: > > Despite this, is it correct to terminate a connection with > > "illegal_parameter" upon receiving a Finished handshake message with a > > 100 byte payload? or a 20 byte payload? My

Re: [TLS] Malformed Finished handling

2018-07-04 Thread Martin Thomson
On Wed, Jul 4, 2018 at 7:55 PM Hubert Kario wrote: > Despite this, is it correct to terminate a connection with "illegal_parameter" > upon receiving a Finished handshake message with a 100 byte payload? or a 20 > byte payload? My opinion is that it is not, "decode_error" is more specific so > it s

Re: [TLS] Malformed Finished handling

2018-07-04 Thread Eric Rescorla
On Wed, Jul 4, 2018 at 6:36 AM, Hubert Kario wrote: > On Wednesday, 4 July 2018 15:00:18 CEST Eric Rescorla wrote: > > I think it's a close call, because the length is sort of external to the > > language. > > which language? the decode_error alert description literally says "length > of > the me

Re: [TLS] Malformed Finished handling

2018-07-04 Thread Salz, Rich
>if the interpretation of "I know this _message_ _length_ is wrong because > of some other values I negotiated before, so I'll send illegal_parameter" was correct, then overflow_error, decrypt_error and probably few others would also need to be replaced with illegal_parameter..

Re: [TLS] Malformed Finished handling

2018-07-04 Thread Hubert Kario
On Wednesday, 4 July 2018 15:00:18 CEST Eric Rescorla wrote: > I think it's a close call, because the length is sort of external to the > language. which language? the decode_error alert description literally says "length of the message was incorrect." > That's why, for instance, NSS sends "ille

Re: [TLS] Malformed Finished handling

2018-07-04 Thread Eric Rescorla
I think it's a close call, because the length is sort of external to the language. That's why, for instance, NSS sends "illegal_parameter". So, absent specific text about this value, I think this is something we can leave to the implementations. -Ekr On Wed, Jul 4, 2018 at 2:54 AM, Hubert Kari

[TLS] Malformed Finished handling

2018-07-04 Thread Hubert Kario
Despite this, is it correct to terminate a connection with "illegal_parameter" upon receiving a Finished handshake message with a 100 byte payload? or a 20 byte payload? My opinion is that it is not, "decode_error" is more specific so it should be used instead. Specification says the following