Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-21 Thread Daniel Bratell
LGTM3 /Daniel On 2024-03-20 23:54, Mike Taylor wrote: LGTM2. Good luck! On 3/20/24 4:30 PM, Yoav Weiss (@Shopify) wrote: LGTM1 On Wed, Mar 20, 2024 at 8:35 PM David Adrian wrote: > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? Both? Something else

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-20 Thread Mike Taylor
LGTM2. Good luck! On 3/20/24 4:30 PM, Yoav Weiss (@Shopify) wrote: LGTM1 On Wed, Mar 20, 2024 at 8:35 PM David Adrian wrote: > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? Both? Something else entirely? We also worked with a variety of vendors to fix

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-20 Thread Yoav Weiss (@Shopify)
LGTM1 On Wed, Mar 20, 2024 at 8:35 PM David Adrian wrote: > > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? > Both? Something else entirely? > > We also worked with a variety of vendors to fix incompatibilities that > were brought to our attention, including Vercel,

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-20 Thread 'David Adrian' via blink-dev
> What's our plan to mitigate that risk? Slow rollout? Enterprise policy? Both? Something else entirely? We also worked with a variety of vendors to fix incompatibilities that were brought to our attention, including Vercel, ZScaler, and PayPal CN (who have all since patched prior to any level

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-19 Thread Yoav Weiss (@Shopify)
On Tue, Mar 19, 2024 at 10:23 PM David Benjamin wrote: > > I'm guessing we're talking about MITM middleboxes, is that correct? > > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? > Both? Something else entirely? > > Whether the middlebox MITMs the TLS connection is not

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-19 Thread David Benjamin
> I'm guessing we're talking about MITM middleboxes, is that correct? > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? Both? Something else entirely? Whether the middlebox MITMs the TLS connection is not terribly important. As long as they attempt to parse the

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-19 Thread Mike Taylor
Also, would you mind requesting reviews for the various shipping gates (privacy, security, enterprise, etc.) in your chromestatus entry? On 3/19/24 12:34 PM, Yoav Weiss (@Shopify) wrote: On Mon, Mar 18, 2024 at 3:37 PM 'David Adrian' via blink-dev wrote: Contact emails

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-19 Thread Yoav Weiss (@Shopify)
On Mon, Mar 18, 2024 at 3:37 PM 'David Adrian' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsdadr...@google.com > > Explainer > https://www.ietf.org/archive/id/draft-tls-westerbaan-xyber768d00-02.html > > Specification >

[blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

2024-03-18 Thread 'David Adrian' via blink-dev
Contact emailsdadr...@google.com Explainer https://www.ietf.org/archive/id/draft-tls-westerbaan-xyber768d00-02.html Specification https://www.ietf.org/archive/id/draft-tls-westerbaan-xyber768d00-02.html Summary Protect current Chrome TLS traffic against future quantum cryptanalysis by