Chromium 114.0.5735.133 packages address critical bug

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

27 thoughts on “Chromium 114.0.5735.133 packages address critical bug

  1. Thanks Eric.
    Installed chromium-114.0.5735.133-x86_64-1alien and chromium-ungoogled-114.0.5735.133-x86_64-1alien this morning.
    Posting from chromium-ungoogled-114.0.5735.133-x86_64-1alien and it is working very well as always.
    — kjh

  2. Thanks Eric! Do you know of any reason why the Chromium-ungoogled package is bigger this time compared to the Chromium package? I see it’s because of the chromedriver file being about 15 MB bigger in the chromium-ungoogled package.

    1. I can’t tell you what went into the chromedriver binary. Perhaps its the content needed to display the page “chrome://ungoogled-first-run/” which was added for this release, and which gives new users of Un-googled Chromium some pointers to get started.
      You can open “chrome://ungoogled-first-run/” at any time in your chromium-ungoogled by the way.

      1. Thanks for your answer. Still, 16.5 MB for a webpage seems a little much. I guess I’m just a little suspicious sometimes…

      2. The strange thing is, the source code for 114.0.5735.133 is actually 15 MB smaller than 114.0.5735.106. But I don’t understand much about the relationship between the source size and the build size…

      3. I’m sorry, I stand corrected, it’s only 15 KB. I guess the main part of the build is the Chromium source download which is then stripped from all Google code…

        1. Well, the chromium source code tarball is used un-modified. The patches are in the ungoogled-chromium tarball which is not distributed by Google – obviously.
          I advise you to build chromium from source yourself if you want to learn why the size of a binary file changed after applying un-googling patches. I really don’t have time for that kind of luxury.

  3. Pingback: Links 18/06/2023: More Microsoft Spyware and Windows Breaches | Techrights

  4. Thanks for chromium-114.0.5735.198-x86_64-1alien and chromium-ungoogled-114.0.5735.198-x86_64-1alien Eric.
    Posting from chromium-ungoogled-114.0.5735.198-x86_64-1alien and it all works very well as expected.
    Thanks again
    — kjh

  5. Thanks Eric for chromium-115.0.5790.170-x86_64-1alien and chromium-ungoogled-115.0.5790.170-x86_64-1alien
    Posting from chromium-ungoogled-115.0.5790.170-x86_64-1alien on Slackware64 15.0 + Multilib and everything works well as usual.
    — kjh

      1. I think there are a lot more people profiting from your work (and being grateful for it) then you think. Some take it for granted , you know how it goes. But please don’t underestimate the importasnce of your work!

        1. Hi Eric,
          Marco is right, there are many people who enjoy your packages and who don’t always post their gratitude in your blog (I’m one of them).
          Not to find any excuse for not posting more often here, but Slackware community gave us such great tools to maintain our system (slackpkg+, sbopkg) that we don’t have/need to constantly check for updates in our browser.
          So let me take this opportunity to thank you again for your great work for the Slackware community, not just the packages but also liveslak and your well-written blog posts.

    1. Thanks for all the updates Eric !
      I’ve installed the list below on Slackware64 15.0 +MultiLib and all work well:
      — kjh

        1. oops !
          keepassxc squeaked by … I missed it !
          Thanks for the heads up, Eric.
          — kjh

          # before:
          # ver keepassxc
          -rw-r–r– 1 root root 4715 Mar 23 2022 /var/log/packages/keepassxc-2.6.6-x86_64-1alien

          # after
          # ver keepassxc
          -rw-r–r– 1 root root 5063 Aug 18 16:09 /var/log/packages/keepassxc-2.7.6-x86_64-1alien

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.