https://revoked.grc.com/

  • 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.)

A

a viewer

Well-known member
Sep 30, 2020
87
19
guess it just has a propagation delay

It shows some sort of this error for safari, firefox and brave

Screenshot 2024-08-07 at 18.28.00.png
 
  • Like
Reactions: Darcon
I think the current thinking is that revoked certificate had a specified validity stabled to it with OCSP stapling. That caused it to look valid for that period, but now that it has expired, it no longer has anything to support it and so the browsers are now failing it.
 
PHolder said:
I think the current thinking is that revoked certificate had a specified validity stabled to it with OCSP stapling. That caused it to look valid for that period, but now that it has expired, it no longer has anything to support it and so the browsers are now failing it.
Click to expand...
the cert didn't expire, it was revoked. Browsers check to see if a cert has been revoked. The problem mentioned was about propagation and not validity. On Tuesday the browsers considered the cert valid

Screenshot 2024-08-08 at 0.35.31.png
 
I concur with others, that it seems that it is a slow propagation before the browser gets a clue.
For the record, Chrome, and Edge also gave me revoked.
 
Same for Safari on iOS 17.6.1
IMG_1959.png
IMG_1960.png


If the site stapled a OCSP validity assertion, which is the current theory, the browser probably honoured it (given it was still valid).
 
  • Like
Reactions: Darcon
You must log in or register to reply here.
Top Bottom
Back