Tag: cve (Page 2 of 22)

You have surely noticed an increase in the frequency with which I am releasing new chromium and chromium-ungoogled packages. This is caused by a new release policy from Google, with an update every week and a bump in the major version (currently 117) every month.
I have tried keeping up with that schedule, but I am giving up.
My reasons? One chromium or chromium-ungoogled package takes 11+ hours to compile (part of the Chromium compilation involves compiling Google’s customized clang compiler). Every update, I need to compile 4 packages. It takes away the fun in updating them to be honest. I don’t know for whom I actually create the 32bit packages still.

So, from this moment onwards, my own package release policy changes as follows. I will keep up with the Google source release cycle, but only for the 64bit packages. My 32bit packages for chromium and chromium-ungoogled will be updated no more than once per month, unless there’s a big security hole to be patched.

By the way, I uploaded new chromium packages for 117.0.5938.149 yesterday and today I added its chromium-ungoogled sibling (64bit only).

Find the updated Slackware 15.0 and -current packages both for chromium and chromium-ungoogled in my repository and its mirrors (like my own US server and in a short while, the UK mirror).

Cheers, Eric

Chromium, regular and un-googled.

Earlier this week, Google released its 114.0.5735.133 update for Chromium 114.
This is a bugfix release and on the list of addressed security issues, there’s one which is labeled as ‘critical‘, labeled CVE-2023-3214. Three other fixes are labeled with a vulnerability rating of ‘high‘.
As always, it is wise to upgrade to my latest chromium and chromium-ungoogled packages.

The updated Slackware 15.0 and -current packages both for chromium and chromium-ungoogled are available in my repository and its mirrors (like my own US server and in a short while, the UK mirror).

Cheers, Eric

Last week the Chromium source code major version was upped to 112. According to the developer blog, this release addresses 16 security issues, none of them critical. Nevertheless, better safe than sorry, so the Slackware packages (15.0 and -current) for Chromium are now ready for downloading from my repository or any of its mirrors. Likewise chromium-ungoogled.

The regular as well as the Un-googled Chromium browser is now at version 112.0.5615.49.
Let’s see what version 113 brings next month – it should have enabled WebGPU by default on ChromeOS even though the Linux builds of Chrome seem to have to wait a bit longer. I wonder if it’s just compile options that I could try to exploit for my Chromium build. I am also curious to see where WebGPU is going to be used in 3D-rendered web applications.

Enjoy! Eric