avenged110
commented
11 months ago Crashes appear to have been fixed with release 120.0.6099.71.2 (at least for me).
Closed RJVB closed 11 months ago
avenged110
commented
11 months ago Crashes appear to have been fixed with release 120.0.6099.71.2 (at least for me).
Wowfunhappy
commented
11 months ago Yep, I think this can be closed, seems to be fixed!
RJVB
commented
11 months ago Yep, I think this can be closed, seems to be fixed!
I'll check later today. Depending on whether or not the entitlements issue is also fixed I'll make the ticket about that (if possible) since it's already mentioned in the OP.
RJVB
commented
11 months ago I'll make the ticket about that (if possible) since it's already mentioned in the OP.
Done!
RJVB
commented
11 months ago Possibly related:
My current session (restored on startup) has 2 github tabs open. If I quit Chromium properly logged in (according to both tabs) and restart the browser with one of the tabs open it will come up "logged in" after the restart. When I switch to the other tab it will also appear to be logged in but with a message You signed in with another tab or window. Reload to refresh your session. and after the reload I will be logged out.
This login will require a 2-factor security code, which I think is not normally the case for recognised browsers (but does correspond to the fact that instagram and facebook both do not remember my logged-in state nor the browser.
RJVB
commented
11 months ago It turns out that I'm also getting these errors with Chromium not running; they appear to indicate that something is not entirely right with my Keychain data/settings. Or simply that that security framework tries to phone home and (or simply) encounters an expired certificate; I appear not to be the only user who sees these, without further issues, apparently.
I think it does mean that the newer Chromium does more frequent access to the keychain.
I'll leave this open for a bit longer to see what else comes up or if someone has anything to chime in with.
krackers
commented
11 months ago Tried clearing keychain entirely (maybe create a new user account, or boot into guest mode or something)?
RJVB
commented
11 months ago Tried clearing keychain entirely (maybe create a new user account, or boot into guest mode or something)?
No, but I might try that or at least test from one of my other accounts.
The curious thing is that I'm not aware that I'm getting these messages when other applications try to get credentials from the keychain, e.g. the Finder when mounting an encrypted disk. I did pick up somewhere that there's a deprecated API for getting keychain info which suggests there's also a newer one... and it would stand to reason that's the one Chromium is using.
And the question is why Chromium would try to access the keychain so often when it hasn't stored creds in there since well before support for 10.9 was dropped.
RJVB
commented
11 months ago Well, besides Chromium accessing the keychain in a way that triggers lots of these messages the underlying issue is apparently a system-wide. I got the same with a barebones backup admin account as soon as I opened the keychain utility.
Describe the bug The latest stable releases (120.0.6099.71.1 and 2) generate lots of security-related errors that appear to be the result of inappropriate/missing entitlements.
To Reproduce Steps to reproduce the behaviour:
Expected behaviour No secd errors
Desktop (please complete the following information):
Logs From the system.log:
with 120.0.6099.71.1 :
With 120.0.6099.71.2 :
I cannot yet tie them to a particular action on a site in question; I've seen them appear when activating sound in IG stories for instance.