RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

. From: Ari Chivukula Sent: Friday, June 20, 2025 3:04 PM To: Rick Byers Cc: Erik Anderson ; Will Harris ; Jeremy Roman ; Domenic Denicola ; blink-dev ; Andrew Williams ; Mike Taylor Subject: Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows I

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

*Sent:* Thursday, June 19, 2025 6:50 PM >> *To:* Will Harris ; Erik Anderson < >> erik.ander...@microsoft.com> >> *Cc:* Jeremy Roman ; Domenic Denicola < >> dome...@chromium.org>; blink-dev ; Andrew >> Williams ; Mike Taylor >> *Subject:* [EXTERNAL

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

> > *From:* Ari Chivukula > *Sent:* Thursday, June 19, 2025 6:50 PM > *To:* Will Harris ; Erik Anderson < > erik.ander...@microsoft.com> > *Cc:* Jeremy Roman ; Domenic Denicola < > dome...@chromium.org>; blink-dev ; Andrew > Williams ; Mike Taylor > *Subject:*

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

: Will Harris ; Erik Anderson Cc: Jeremy Roman ; Domenic Denicola ; blink-dev ; Andrew Williams ; Mike Taylor Subject: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows Not to my knowledge, but I'm adding @erik.ander...@microsoft.com<mailto:er

Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

Not to my knowledge, but I'm adding @erik.ander...@microsoft.com in case there is something I missed. I'm fine with starting with 22H2+ only for now, and adding 20H1+ only if there's a reliable way to detect the fix or metrics on fix rollout % that are convincing. ~ Ari Chivukula (Their/There/Th

Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

in general, it's preferable to do a capability test via an OS API rather than simply gate on Windows version. Does the new API that Microsoft added (and backported) provide a way for the OS to signal that this better/working API is available? Will On Thu, Jun 19, 2025 at 11:15 AM Ari Chivukula w

Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

That's probably possible, though hopefully they have installed system updates in the past year. We could just target 2022H2 and later if needed. ~ Ari Chivukula (Their/There/They're) On Thu, Jun 19, 2025 at 10:54 AM Jeremy Roman wrote: > > > On Thu, Jun 19, 2025 at 12:10 AM Domenic Denicola >

Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

I'm also not sure it needs API Owner approval, but I'll second Domenic: LGTM2 (It does get some extra visibility this way which might be helpful, especially if it triggers some unexpected problems) /Daniel On 2025-06-19 06:10, Domenic Denicola wrote: I believe this should be completely unobs

Re: [blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

On Thu, Jun 19, 2025 at 12:10 AM Domenic Denicola wrote: > I believe this should be completely unobservable to web authors, right? > (Apart from maybe fewer or more network errors.) > > If so, I don't think this needs any LGTMs, as it fits well under the > Web-developer-facing > change to existi

[blink-dev] Re: Intent to Ship: Randomizing TCP Port Allocation on Windows

I believe this should be completely unobservable to web authors, right? (Apart from maybe fewer or more network errors.) If so, I don't think this needs any LGTMs, as it fits well under the Web-developer-facing change to existing behavior