Re: [TLS] Server abort because of unrecognised vs rejected client provided parameters

2016-10-27 Thread Hubert Kario
On Thursday, 27 October 2016 19:46:40 CEST Kurt Roeckx wrote: > On Fri, Oct 21, 2016 at 03:24:35PM +0200, Hubert Kario wrote: > > Currently TLS has two alert descriptions for when there is no intersection > > between ciphers/sigalgs/groups advertises by client and ones that are > > enabled in serve

Re: [TLS] Server abort because of unrecognised vs rejected client provided parameters

2016-10-27 Thread Kurt Roeckx
On Fri, Oct 21, 2016 at 03:24:35PM +0200, Hubert Kario wrote: > Currently TLS has two alert descriptions for when there is no intersection > between ciphers/sigalgs/groups advertises by client and ones that are enabled > in server. It's the handshake_failure and insufficient_security alerts. > >

[TLS] Server abort because of unrecognised vs rejected client provided parameters

2016-10-21 Thread Hubert Kario
Currently TLS has two alert descriptions for when there is no intersection between ciphers/sigalgs/groups advertises by client and ones that are enabled in server. It's the handshake_failure and insufficient_security alerts. While it is a step in good direction in providing users with better mes