4 ms·
They are running a Chrome from 2016, so they are vulnerable to ~every exploit found in Chrome since then.
by evmar 4y ago
They are running a Chrome from 2016, so they are vulnerable to ~every exploit found in Chrome since then.
- nine_k 4y agoWon't a modern version of Chromium build for XP, with some tweaking?
- hippich 4y agoFrom my experience, there is a lot of software that will not build for platform older than 7/2008 due to missing APIs. Visual studio stopped support for xp compilation awhile ago. You still can use clang or such for simple programs today, but chromium is probably too complicated to port at this point.
- jamesfinlayson 4y agoI thought I saw it in Visual Studio 2019 but I'm misremembering - Visual Studio 2017 was the last to support building for Windows XP by the looks of it.
- planede 4y agoChromium already builds with clang + libc++ on every platform, including Windows.
- evmar 4y agoI was curious so I found the bug where they tracked some of the post-XP cleanup work: https://bugs.chromium.org/p/chromium/issues/detail?id=579196 https://bugs.chromium.org/p/chromium/issues/detail?id=579196
- mikae1 4y agohttps://github.com/blueboxd/chromium-legacy https://github.com/blueboxd/chromium-legacy exists for macOS, so it would only be fair if there was something similar for old versions of Windows. :)
- hulitu 4y agoThat's not how (modern) SW works. Ever heard of "new features and security improvements" ?
- KyeRussell 4y agoWhat? This is certainly how not updating Chrome works.
- hulitu 4y agoThey even took "security" out. On Android: "Thanks for choosing Chrome! This release includes stability and performance improvements."