Re: [TLS] What's it called

Depends on the algorithm and its parameters. Here is a recent document talking about AES algorithms limits. https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-aead-limits-02 From: TLS On Behalf Of Tim Bray Sent: Thursday, June 24, 2021 9:13 PM To: Paterson Kenneth Cc: tls@ietf.org; Salz, Ric

Re: [TLS] What's it called

On Fri, Jun 25, 2021, at 05:13, Tim Bray wrote: > How much data is too much? https://cfrg.github.io/draft-irtf-cfrg-aead-limits/draft-irtf-cfrg-aead-limits.html ...shameless self-promotion. ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman

Re: [TLS] Editorial: chronological order in ECH draft

Thanks for the feedback, all! > On Jun 23, 2021, at 4:50 PM, Christopher Patton > wrote: > > +1 to new readers! I think a chronological description would be a good > starting point, though like MT, I suspect there would be rearranging to do > afterwards that would break with a strictly chrono

Re: [TLS] What's it called

I've heard the phenomenon called "exhaustion" and "rekey" the fix for it. On Thu, Jun 24, 2021 at 11:52 AM Salz, Rich wrote: > Rekey and safety margin work for my purposes. Thanks everyone! > ___ > TLS mailing list > TLS@ietf.org > https://www.ietf.or

Re: [TLS] What's it called

How much data is too much? On Thu, Jun 24, 2021 at 12:02 PM Paterson Kenneth < kenny.pater...@inf.ethz.ch> wrote: > Hi Rich, > > > > We speak of reaching data limits, and the process of changing the key has > many names, e.g. key rotation, key renewal, key refreshing, key updating. > > > > Any of

Re: [TLS] What's it called

Hi Rich, We speak of reaching data limits, and the process of changing the key has many names, e.g. key rotation, key renewal, key refreshing, key updating. Any of those ring a bell? Cheers Kenny From: TLS on behalf of "Salz, Rich" Date: Thursday, 24 June 2021 at 19:32 To: "tls@ietf.org"

Re: [TLS] What's it called

Rekey and safety margin work for my purposes. Thanks everyone! ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] What's it called

We rekey when certain limits are hit. Is there a common name for those limits? ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] What's it called

Do youmean key rotation or rekeying? I'd check Lukx Paterson https://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf Limits on Authenticated Encryption Use in TLS All the best Tanja On Thu, Jun 24, 2021 at 05:31:58PM +, Salz, Rich wrote: > I’m blanking on a term and web searches turn

Re: [TLS] What's it called

Dear Rich, Rekeying (https://datatracker.ietf.org/doc/html/rfc8645). For GOST, the "key meshing" term at least was in use. On Thu, Jun 24, 2021 at 7:32 PM Salz, Rich wrote: > I’m blanking on a term and web searches turn up too much useless info. > > > > What is it called when we have to start u

Re: [TLS] What's it called

I've heard this called "rekeying". The amount of data that's safe to authenticate and encrypt is usually called the "safety margin". Chris P. On Thu, Jun 24, 2021 at 10:32 AM Salz, Rich wrote: > I’m blanking on a term and web searches turn up too much useless info. > > > > What is it called whe

[TLS] What's it called

I’m blanking on a term and web searches turn up too much useless info. What is it called when we have to start using a new symmetric key because we’ve encrypted too much data with the old one? Key exhaustion fits, but probably isn’t it. ___ TLS mail

[TLS] Fwd: [Uta] RFC 7525bis (TLS BCP) and ChaCha-Poly

FYI for those not on the UTA WG list. Please discuss there. /psa Forwarded Message Subject:[Uta] RFC 7525bis (TLS BCP) and ChaCha-Poly Date: Thu, 24 Jun 2021 12:34:59 +0300 From: Yaron Sheffer To: u...@ietf.org Hi,   Here’s to remind the working group that

Re: [TLS] Upgrading TLS session resumption from TLS 1.2 to TLS 1.3?

Ah, okay. That's unfortunate, tho, resumption upgrades would be useful with TLS-SRP, to get the benefits TLS 1.3 brings without having to update login details. Thanks tho. On 2021-06-24 12:11 p.m., David Benjamin wrote: > No, resumption should happen after version negotiation, and be > declined i

Re: [TLS] Upgrading TLS session resumption from TLS 1.2 to TLS 1.3?

No, resumption should happen after version negotiation, and be declined if inconsistent. The way it works is: 1. Suppose the client previously connected to the server and received a TLS 1.2 session. It connects again. The client supports TLS 1.2 and 1.3, but doesn't know a priori whether the serve

[TLS] Upgrading TLS session resumption from TLS 1.2 to TLS 1.3?

What's the story on backwards compatibility between TLS 1.2 session resumption and TLS 1.3 session resumption? Appendix D. Backward Compatibility doesn't seem to say anything about it. It seems like TLS 1.2 session resumption is gonna keep using TLS 1.2 even if both sides support TLS 1.3?