On Tue, 2017-04-11 at 13:47 -0700, Eric Rescorla wrote:
> > 4.1.1. HelloRetryRequest how many times can it be re-sent by the
> > server? I assume only a single one, but it maybe good to make it
> > explicit.
>
> This is forbidden in S 4.1.4.
> https://tlswg.github.io/tls13-spec/#hello-retry-reque
> Speaking as one of the co-authors of [1]: it is not completely clear to me
> what
> is the limitation in CT that would prevent it to cope with the pervasive use
> of
> short-term certificates. Can anyone shed a light on this?
I believe the concerns are scaling log servers and perhaps needing
On 21/04/2017 11:48, "TLS on behalf of Ilari Liusvaara" wrote:
On Fri, Apr 21, 2017 at 10:37:21AM +0200, Hannes Tschofenig wrote:
> > What is also not clear to my why some of the certificate management
> > protocols, which provide the necessary level of automation, cannot be
> > used with CAs to r
On Fri, Apr 21, 2017 at 10:44:01AM +0200, Hannes Tschofenig wrote:
> I have read draft-sullivan-tls-exported-authenticator-01 and have a few
> questions. I haven't followed this work previously but have been
> wondering whether this functionality would be useful for "me".
>
> The described functio
On Fri, Apr 21, 2017 at 10:37:21AM +0200, Hannes Tschofenig wrote:
> I read through draft-rescorla-tls-subcerts-01 and I ran into some basic
> questions.
>
> I have been wondering why the TLS server operator obtains an end-entity
> certificate from a CA (which cannot be used to sign further
> cert
I have read draft-sullivan-tls-exported-authenticator-01 and have a few
questions. I haven't followed this work previously but have been
wondering whether this functionality would be useful for "me".
The described functionality sounds like post-handshake authentication
from TLS 1.3 (although it do
I read through draft-rescorla-tls-subcerts-01 and I ran into some basic
questions.
I have been wondering why the TLS server operator obtains an end-entity
certificate from a CA (which cannot be used to sign further
certificates) instead of running an intermediate CA him-/herself
instead. This woul
Hi Ben,
thanks for your remark.
I don't think that this is an issue in DTLS since the epoch field
provides additional information to properly select the correct key.
Ciao
Hannes
On 04/20/2017 04:34 PM, Benjamin Kaduk wrote:
> On 04/20/2017 01:22 AM, Hannes Tschofenig wrote:
>>
>> On 04/19/2017 0