IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Wade is likely right + couple of things to check
The full chain is
www.kqed.org: from 03/21/2019 to 03/21/2021
Sectigo RSA Extended Validation Secure Server CA: 11/02/2018 - 12/31/2030
USERTrust RSA Certification Authority: 02/01/2010 - 01/18/2038

Check the Mac's keystore for those last two. It is possibly to locally mark certificates as untrusted, so check for that as well.

The few times I tried, I've found Safari upgrades to be tied to OS upgrades. Unless Apple recently changed it's mind, you may have to install missing certs manually.
New Going there:
Keychain Access.app invoked; options:
All Items
Passwords
Secure Notes
My Certificates
Keys
Certificates ... [pity: no bloody Cut/Paste, just stone-knives. bearskins to re-write]

[All Items] 17 items (incl "CUPS Self-Signed Certificate", as 'private key': more below on That] no mention of 'Sectigo'
Also: https://talkingpointsmemo.com/edblog/surveying-the-whirlwind AS: c-73-158-167-161.hsd1.ca.comcast.net

Thence root-login and display of that last "c-73-i58 item ... gets new window:

Icon says: [Certificate; below that: Root] Its bolded header IS ""c-73-i58 item" and last line of Intro sez, This root certificate is not trusted [in Red]
It seems that I can delete this entry.. maybe should but await Instruction. Presumably the other 16 items will continue to operate unremarkably.

If I focus on mentioned CUPS line, Rt-click gets {Sigh} more options:
Copy, Paste, Delete
Export
Get info
Create a Cert w/Cups ditto
Request a Certificate From a Certificate Authority w/ditto-name
Create a Certificate Authority With w/ditto-name

{Particle accelerators are more complex but sans boring, endless drill-downs of arbitrary /opaque intent :-/

Sorry if this is too-much; sorrier if it's not-Enough, eh? n-Thanks for sharing the Excitement of RED-things appearing.
Is it likely that simply Deleting that reddish-LINE can undo the Evil black-listing of kqed?
I'm All Ears, (Ah feels the Power of ... Admin-for ..a couple hours) ;^>

Repeat: Sectigo appears nowhere atop/within any of these texts.
Checking 'Spotlite', for giggles: Nope, That doesn't find any iteration save the obvious refs re this Query,

Over /Out ... need some Southrun Comfort in the coffee, lest lapsing into a crazed .. ...rm -r hda0
New Don't nuke the CUPS certificate
CUPS is Apple's print server setup. It is essentially a tangled set of web services and these days, encryption is enabled by default. Kill the cert and your printer may stop talking to you.

Self-signed means the cert isn't trusted beyond the local computer. That is fine for the use CUPS puts it to.

c-73-158-167-161.hsd1.ca.comcast.net is the Comcast hostname for a residential (dynamic) IP address (73.158.167.161). I can't say why Apple would have it in the keychain but if Comcast is your ISP, then it could be your cable modem.

TPM draws a "Connection not secure" error because the protected page contains unprotected links. That complaint is genuine, it is not due to a certificate problem.

If all else fails and the problem persists, you can manually download and install the cert chain from Sectigo (although, based on your adventures further down, you may have to override Safari's error dialogs.)
Expand Edited by scoenye June 1, 2020, 10:48:51 PM EDT
New Gracias..
Discovered *CUPS back in the Knoppix days, should have recalled that (guess I imagined that, if nuked, it would re-create-self on a reboot). Part-2: but not if it calls the same cert from same place. Duh.
* even managed to make it er, Print {pats ego mildly}.

In any event -- I didn't. :)

As to Box's confirmation of similar conflagration, surely we'll hear soon (?) if this was Vlad-the-Impaler or similar.
Don't care lots about the silly-level inconvenience; next: is someone fabricating an App, should this fix need a bit of individual action by multitudes..

Apreciate the brain-work, again.
     I'm back; this time re "Sectigo" - (Ashton) - (21)
         Sounds like an update is needed. - (static)
         Also, thanks. - (static)
         Wade is likely right + couple of things to check - (scoenye) - (3)
             Going there: - (Ashton) - (2)
                 Don't nuke the CUPS certificate - (scoenye) - (1)
                     Gracias.. - (Ashton)
         Here's a page that might help, if you can get there. - (Another Scott) - (1)
             Hm: gives important also-too CLUE! (Can't Go-->There, either) - (Ashton)
         Something happened with SSL certs yesterday - (malraux) - (11)
             Thanks.. helps out, 'the Loneliness of the Long-distance tyro-Debugger .. a bit :-) -NT - (Ashton) - (10)
                 major cert trust domain issue yesterday - (boxley) - (9)
                     CRL lookup service blowout? The only thing I can think of that would cause widespread mayhem. -NT - (scoenye) - (3)
                         Heh.. that moniker sent moi --> Belgium and a ∆ re (my) access to Sectigo. - (Ashton) - (2)
                             That is what is going on - (scoenye) - (1)
                                 Excellent--Lots of peripheral info there too; Bonus. -NT - (Ashton)
                     Still going on. - (malraux) - (4)
                         we use a gummint cert internal to ourselves - (boxley) - (3)
                             We didn't have browser issues - (malraux) - (2)
                                 Sectigo's SHA-1 root + intermediate certs expired. - (scoenye) - (1)
                                     I don't think that's all that happened. - (malraux)
         Teapot; Tempest-in: Thanks all! stuff works. The post-mortem amusement awaits.. -NT - (Ashton)

We're gonna make this night... last fo-evah!
89 ms