(GoogleChrome) Windows Server 2012 R2 and Windows 8.1 Chrome security patch builds

[AdamDeCelis]

Before starting, ensure that you have done the following.

• I have verified that there is no other issue or discussion covering the feature or enhancement
• I have verified there is no open pull request for the feature or enhancement
• I have verified the package to improve is located in this repository

What do you want to add?

I'd like to request that version 109.0.5414.149 be made available as updates for systems running Windows Server 2012R2 and Windows 8.1 as these include security patches for the recent Chrome exploits and these and older Windows OS versions are unable to update to Google Chrome 110+

The latest version that these OS's can update to via Chocolatey is 109.0.5414.120 which leaves systems vulnerable

Google provide these special releases for older Windows operating systems from the below URLs:

Google Chrome 32 Bit MSI - Build 109
Google Chrome 64 Bit MSI - Build 109

See article from Google here:

Sunsetting support for Windows 7 / 8/8.1 and Windows Server 2012 and Windows Server 2012 R2 in 2023

Google are providing critical security patch versions for these OS versions until they are EOL in October 2023.

What problem will the feature/enhancement solve?

This will allow for chocolatey to patch Google Chrome versions on older operating systems to include critical security fixes for known exploits

If the feature or enhancement is approved:

• I am willing to create a pull request to implement the feature or enhancement

Additional Context

This also affects other Chromium based browsers such as Edge and Brave. But Google Chrome is the most common so I thought it best to have it implemented here first.

Feel free to contact me here, or via the Disqus chat in the choco repository if you need further information.

[pauby]

As Google only produces one setup file, it's not possible to have specific versions in the packages. As that version had already been approved, it's not possible to go and update it with the installer versions you mentioned.

It may be possible to push a package fix version that would be 109.0.5414.121 (note the last number is incremented).

That would be a very manual process that one of the repository maintainers would have to agree to pick up as I don't think we could have a PR for it as that would affect the automation.

[AdamDeCelis]

And the latest 109 available in choco isn't the latest version Google host

[pauby]

They can't update past 109 versions it fails ever since 110 was released, they can't get to the latest version of 109 even if they are on 108 unless they specify the version number

That's why I suggested they pin at that package version.

And the latest 109 available in choco isn't the latest version Google host

That's why I suggested that the version be pushed above and @TheCakeIsNaOH highlighted that the version the Chocolatey Community Repository have is the latest.

[pauby]

I've created a branch over on my packages' repository for this. There may be a better way of doing it, but I didn't want to disturb anything in here.

The package has been tested on the Chocolatey Test Environment (Windows Server 2019). I don't have a VM that this version is specifically for, but it shouldn't make any difference. It installs version 109.0.5414.149. However, it would be good if others could test this.

I am happy to be added as a maintainer, push this version, and then remove myself again.

[pauby]

@AdamDeCelis are you still interested in this package?

[AdamDeCelis]

Cheers for that... I'll check it out next time I have to work on a 2012 server