I guess I’m somewhat unconvinced, seeing that one other person plus myself saw precisely the same messages you were reporting. I wouldn’t think we all had identical corruption.
On Apr 24, 2015, at 9:04 PM, Carl Hoefs <newsli...@autonomy.caltech.edu> wrote: > It turns out that there are numerous reasons this error can appear (firewall > issues, expired/corrupted certs, incorrect system time, etc.). There’s a neat > feature in the Keychain.app menu bar called “Keychain First Aid” that allows > you to repair a corrupted keychain configuration. I ran that and it detected > something that was corrupted and repaired it (sorry, I should have saved the > output). Anyway now Safari seems to be silent. I’m keeping my fingers crossed > that the issue doesn’t come back! > Thx, > -Carl > > _______________________________________________ > MacOSX-talk mailing list > MacOSX-talk@omnigroup.com > http://www.omnigroup.com/mailman/listinfo/macosx-talk _______________________________________________ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
