Re: [webkit-dev] Request for position: Removing 3DES from TLS

2021-04-29 Thread David Benjamin via webkit-dev
Ah yes, that is confusing. Not quite. What's going on here is that we've moved 3DES (and SHA-1 server signatures) under a fallback connection, so our first connection won't advertise them, but on error the second one will. This means that, for compatibility and security purposes, we *do* support

[webkit-dev] Request for position: Removing 3DES from TLS

2021-04-28 Thread David Benjamin via webkit-dev
Hello WebKit friends, We're looking at dropping 3DES cipher suites from TLS. For us, this is just TLS_RSA_WITH_3DES_EDE_CBC_SHA. Looks like Safari additionally supports TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA and TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, which would also fall under that category. After

Re: [webkit-dev] Request for position: ALPS and ACCEPT_CH HTTP/2 and HTTP/3 frames

2021-04-06 Thread David Benjamin via webkit-dev
On Tue, Apr 6, 2021 at 2:37 PM Alex Christensen wrote: > I’m also wondering why > https://github.com/WICG/client-hints-infrastructure/blob/main/reliability.md#retry-limits > says it should only retry GET requests. Is that just to avoid re-uploading > large POST requests? > POST requests are

Re: [webkit-dev] Request for position: ALPS and ACCEPT_CH HTTP/2 and HTTP/3 frames

2021-04-06 Thread David Benjamin via webkit-dev
(Oops, couldn't post to the list without being subscribed. Apologies for the duplicate mail to anyone who got both!) On Tue, Apr 6, 2021 at 1:02 PM David Benjamin wrote: > Hi Alex, thanks for the comments! Responses inline. > > On Mon, Apr 5, 2021 at 9:04 PM Alex Christensen > wrote: > >> I’m