Computer Hope
Microsoft => Microsoft Windows => Windows XP => Topic started by: Vetal on November 25, 2017, 08:02:51 PM
-
Anyone remember which was the last version that worked on XP?
-
Where would you get an old version anyhow, I mean one that was safe? Cliqz says "For security reasons, we cannot provide older versions of Cliqz that are compatible with Windows XP/Vista." Other sources could be risky. However they do say there is an alternative, Firefox ESR with the Cliqz extension, add an ad-blocker and HTTPS Everywhere, and you’ll end up with a similar package as the Cliqz browser.
-
Where would you get an old version anyhow, I mean one that was safe? Cliqz says "For security reasons, we cannot provide older versions of Cliqz that are compatible with Windows XP/Vista." Other sources could be risky. However they do say there is an alternative, Firefox ESR with the Cliqz extension, add an ad-blocker and HTTPS Everywhere, and you’ll end up with a similar package as the Cliqz browser.
All I need to know is what version I'm looking for. Yes, I got the same exact (almost word for word) malarkey when I contacted the Cliqz homesite. I wrote back and told him if he really thought I would be willing to drop XP, just to try out his browser, then he was delusional. I handle my own safety. Don't need no suckling or burping from Microsoft, or some browser playing at being my Nanny or Nursemaid (that is why Firefox got kicked to the curb). Don't know if Cliqz will be any less obsessed with 'security certificates' til I give it a test drive.
-
The Cliqz Browser is a fork of Firefox. The last version of Firefox for Windows XP was 52. The last version of the Cliqz Browser that was based on Firefox 52 looks to be 1.12.1 based on their release history on github, I'd suspect that is the last version that runs on XP.
It is unlikely that it will treat untrusted Certificates any differently than Firefox. Aside from being based on Firefox, it is a fork that is designed to strengthen security and privacy considerations; ignoring untrusted security certificates certainly goes against that goal.
Realistically, what you need to do is to update the installed root certificates on the system in question. I linked to a Windows XP hotfix in another thread which is also described here (https://support.microsoft.com/en-us/help/931125/how-to-get-a-root-certificate-update-for-windows).
Browsers that support https aren't typically going to ignore a SSL certificate that it cannot verify. More recent browsers have certainly made it harder for people to ignore untrusted certificates, but that is because making it easy causes many users to become victims of their own hubris.