Today, Google rolled out a patch for the 0-day exploit, and that patch is only available for 117 but not 116 extended support. Also, the Google Chrome release channel blog no longer mentions any updates for extended support versions: https://chromereleases.googleblog.com/. As you can see on that page, an update for 117 has been specified but not 116.
Previously, extended support versions continued to get security updates until and unless they were no longer supported. Am I missing something?
Thanks
Lei Zhang
unread,
Sep 28, 2023, 2:16:48 AM9/28/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to asesh.s...@cloudfactory.com, Chromium-dev
116.0.5845.228 and newer has the fix. Check again tomorrow to see if a
new update gets pushed out?
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Asesh Shrestha, Chromium-dev
Since the update with the fix for your 0-day of interest has not been
published yet, why would you expect the release dashboard to show a
non-existent release? Similarly, why would you expect a post on the
release blog about a release that hasn't happened yet?
Asesh Shrestha
unread,
Sep 28, 2023, 5:12:53 AM9/28/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chromium-dev, Lei Zhang, Chromium-dev, Asesh Shrestha
Ok, so when it will be published when it's rolled out. Our Chromium fork uses LTS, so to keep our users safe, we need to sync the latest changes too. That's why I was confused on why those data were not published.