Certificate Revocation in action

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

EdwinG

Well-known member
Sep 24, 2020
72
29
So... one of the major ISPs in Canada has (had) its www certificate revoked.

When you visit https://www.bell.ca/ (as of posting on 2023-03-23 18:46 UTC) using a browser different than Google Chrome, you get the error below (here, Microsoft Edge).
1679596986882.png


Just funny.

Credit to: NeilN over at DigitalHome Forums for finding this :)
 
Steve had a few episodes (and even mentioned it recently with the 90 day TLS certificate life) that Chrome does not handle certificate revocation properly. Chrome has an internal list of certificates that are revoked, and it never sees actual live revocations.

Steve proved this by revoking one of his certificates, and all the browsers except Chrome recognized it. Chrome added this certificate to their internal list of revoked certificates to avoid the negative perception, so Steve created a new one and revoked that again to show the problem still exists. Chrome never bothered to add this second certificate to the internal list.

Chrome is the more dangerous browser to use IMHO which is why it is not installed on any of my systems. Maybe the variants (Vivaldi, Edge, Opera, Brave,...) are using real revocation lists, unless your Edge was not updated to the Chromium version.

People that I support MUST use Firefox or find someone else to help them with their computer issues.
 
Steve had a few episodes (and even mentioned it recently with the 90 day TLS certificate life) that Chrome does not handle certificate revocation properly. Chrome has an internal list of certificates that are revoked, and it never sees actual live revocations.

Steve proved this by revoking one of his certificates, and all the browsers except Chrome recognized it. Chrome added this certificate to their internal list of revoked certificates to avoid the negative perception, so Steve created a new one and revoked that again to show the problem still exists. Chrome never bothered to add this second certificate to the internal list.

Chrome is the more dangerous browser to use IMHO which is why it is not installed on any of my systems. Maybe the variants (Vivaldi, Edge, Opera, Brave,...) are using real revocation lists, unless your Edge was not updated to the Chromium version.

People that I support MUST use Firefox or find someone else to help them with their computer issues.
It‘s the Chromium-based Edge on Windows.

I can also confirm that Firefox on Windows, Safari on macOS and iOS all prevented accessing bell.ca (which, for completeness purposes, is one of the big three ISPs).

I’m aware how the certificate révocation feature on Chrome is broken, and I understand their position. I’m not sure if I find it more disappointing or sad.