Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

On Tue, Sep 19, 2023 at 7:45 AM Yoav Weiss wrote: > > > On Tue, Sep 19, 2023 at 1:35 AM 'Jeffrey Yasskin' via blink-dev < > blink-dev@chromium.org> wrote: > >> On Mon, Sep 18, 2023 at 4:11 PM David Adrian wrote: >> >>> > This should probably be an "Intent to Deprecate and Remove" rather >>>

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

On Tue, Sep 19, 2023 at 1:35 AM 'Jeffrey Yasskin' via blink-dev < blink-dev@chromium.org> wrote: > On Mon, Sep 18, 2023 at 4:11 PM David Adrian wrote: > >> > This should probably be an "Intent to Deprecate and Remove" rather than >> an "Intent to Ship". >> >> You're absolutely right that it

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

On Mon, Sep 18, 2023 at 4:11 PM David Adrian wrote: > > This should probably be an "Intent to Deprecate and Remove" rather than > an "Intent to Ship". > > You're absolutely right that it should be, unfortunately that's not the > subject Chrome Status generated. I'll file an issue. > Oops, yes,

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

> This should probably be an "Intent to Deprecate and Remove" rather than an "Intent to Ship". You're absolutely right that it should be, unfortunately that's not the subject Chrome Status generated. I'll file an issue. > The RFC's introduction at

Re: [blink-dev] Intent to Ship: TLS Encrypted Client Hello (ECH)

> Could we please request a signal? Done (and positive!). I had forgotten to add it to Chrome Status. https://github.com/WebKit/standards-positions/issues/46 As for the explainer, between sending the I2S and now, I updated the Chrome Status description to cover most of what David Benjamin

Re: [blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

This should probably be an "Intent to Deprecate and Remove" rather than an "Intent to Ship". I'll let an API owner say if there's a reason to re-send it; probably there isn't. On Mon, Sep 18, 2023 at 3:47 PM 'David Adrian'

[blink-dev] Intent to Ship: Deprecate TLS SHA-1 server signatures

Contact emailsdadr...@google.com ExplainerNone Specificationhttps://www.rfc-editor.org/rfc/rfc9155.html Summary Chrome is removing support for signature algorithms using SHA-1 for server signatures during the TLS handshake. This does not affect SHA-1 support in server certificates, which was

Re: [blink-dev] Intent to Ship: Enrollment for Privacy Sandbox

Thanks Rick! Responses inline. On Fri, Sep 15, 2023 at 4:55 PM Rick Byers wrote: > LGTM3 > > On the compat front this is technically a breaking change for shipped > APIs. Normally we'd want to see a more thorough a compat analysis > to back up the claim of sites not

[blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org, jsb...@chromium.org, asu...@chromium.org Explainer

Re: [blink-dev] Intent to Ship: TLS Encrypted Client Hello (ECH)

On Mon, Sep 18, 2023 at 10:06 AM Yoav Weiss wrote: > > > On Sat, Sep 16, 2023 at 5:35 PM David Benjamin > wrote: > >> On Sat, Sep 16, 2023 at 1:12 AM Yoav Weiss >> wrote: >> >>> >>> >>> On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor >>> wrote: >>> On 9/11/23 6:34 PM, 'David Adrian' via

Re: [blink-dev] Intent to Ship: Fenced Frames - Functionality Updates

An update on this: The extra input sanitization was merged for M119 behind a feature flag for M119 fenced frame changes. It rejects macros at declaration time whose keys/values use characters that are disallowed in URI components (e.g. &, ?, $, {, } that were most relevant here).

Re: [blink-dev] Intent to Ship: TLS Encrypted Client Hello (ECH)

On Sat, Sep 16, 2023 at 5:35 PM David Benjamin wrote: > On Sat, Sep 16, 2023 at 1:12 AM Yoav Weiss wrote: > >> >> >> On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor >> wrote: >> >>> On 9/11/23 6:34 PM, 'David Adrian' via blink-dev wrote: >>> >>> Contact emails david...@chromium.org,

Re: [blink-dev] Intent to Ship: Private Network Access restrictions for automotive

LGTM2 On Mon, Sep 18, 2023 at 3:16 PM Mike Taylor wrote: > LGTM1. Curious to know (but happy to not know) how many local servers are > running in my car... > On 9/18/23 5:30 AM, Jonathan Hao wrote: > > Contact emails p...@chromium.org > > Explainer >

Re: [blink-dev] Intent to Ship: Private Network Access restrictions for automotive

LGTM1. Curious to know (but happy to not know) how many local servers are running in my car... On 9/18/23 5:30 AM, Jonathan Hao wrote: Contact emails p...@chromium.org Explainer https://github.com/WICG/private-network-access/blob/main/explainer.md

Re: [blink-dev] Intent to Ship: Attribution Reporting features (change registration limit, remove 1hr delay)

LGTM2 On 9/16/23 10:28 AM, Yoav Weiss wrote: LGTM1 On Mon, Sep 11, 2023 at 10:58 PM 'Akash Nadan' via blink-dev wrote: Contact emails johni...@chromium.org, csharri...@chromium.org Explainer https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md

[blink-dev] Re: PSA: WebHID in Extension Service Workers

Hi there, Calling navigator.hid.requestDevice in service worker is not possible, so what is correct way of requesting a device? On Friday, February 17, 2023 at 1:59:14 AM UTC+3:30 Tarek ElBahnasawy wrote: > Contact emailsmattre...@chromium.org, chen...@chromium.org >

[blink-dev] Intent to Ship: Private Network Access restrictions for automotive

Contact emailsp...@chromium.org Explainer https://github.com/WICG/private-network-access/blob/main/explainer.md Specificationhttps://github.com/WICG/private-network-access Design docs https://docs.google.com/document/d/1ozjh-G6faEEkgVp__mjq6c_4U93sS4kK4zoelTE7Awg/edit?usp=sharing Summary