Cc: tls@ietf.org
Subject: Re: [TLS] Antw: Re: Antw: Re: Suspicious behaviour of TLS server
implementations
On Friday, September 23, 2016 1:39 AM, Peter Gutmann wrote:
> Andreas Walz writes:
>
>>However, where would you draw the line between "I can't" and "I don
On Friday, September 23, 2016 1:39 AM, Peter Gutmann wrote:
> Andreas Walz writes:
>
>>However, where would you draw the line between "I can't" and "I don't want
>>to"?
>
> It's one of those judgement-call things, I don't know if you can strictly
> define it but as a rule of thumb I'd say that if
On Friday, 23 September 2016 08:38:44 CEST Peter Gutmann wrote:
> Andreas Walz writes:
> >However, where would you draw the line between "I can't" and "I don't want
> >to"?
>
> It's one of those judgement-call things, I don't know if you can strictly
> define it but as a rule of thumb I'd say tha
Andreas Walz writes:
>However, where would you draw the line between "I can't" and "I don't want
>to"?
It's one of those judgement-call things, I don't know if you can strictly
define it but as a rule of thumb I'd say that if you encounter it during
normal processing it's an I-can't problem whil
On 23 September 2016 at 00:47, Viktor Dukhovni wrote:
>> I see your point here. However, where would you draw the line between "I
>> can't" and "I don't want to"? Think of a cipher suites list with 3 bytes in
>> a ClientHello. You can still find one cipher suite that could be ok to work
>> with
> On Sep 22, 2016, at 8:18 AM, Andreas Walz
> wrote:
>
> I see your point here. However, where would you draw the line between "I
> can't" and "I don't want to"? Think of a cipher suites list with 3 bytes in a
> ClientHello. You can still find one cipher suite that could be ok to work
> with
>>> Peter Gutmann 22.09.16 7.00 Uhr >>>
> Nope. There's a big difference between "I can't continue" and "I can
> continue without any problems but don't want to". The example I gave of
> "Couldn't connect to Amazon because no suitable encryption was available"
> would be the error message to
