The feature can be enabled as follows:
Enable Mac OS X to use the CRL and OCSP to provide protection from invalidated digital certificates. The settings to enable system-wide use of the CRL and OCSP are accessible via Keychain Access. On the "Certificates" pane in the Preferences of Keychain Access, set the following:
Online Certificate Status Protocol (OCSP): Best Attempt
Certificate Revocation List (CRL): Best Attempt
Priority: OCSP
This is in Keychain settings.
(edit: ah, reading comprehension.. anyways, don't tuck the first step in the middle of a long sentence)
For Firefox you can enable security.OCSP.require in about:config.
I'm just going to go ahead and leave this here...
http://www.google.com/chrome/intl/en/landing_chrome_mac.html?hl=en
I'm just going to go ahead and leave this here...
http://www.google.com/chrome/intl/en/landing_chrome_mac.html?hl=en
Mac OS X has a feature where compromised SSL certificates are revoked as soon as the certificates are known to be compromised. Using the feature is a lot better than waiting for an update to fix the issue.
The feature can be enabled as follows:
Enable Mac OS X to use the CRL and OCSP to provide protection from invalidated digital certificates. The settings to enable system-wide use of the CRL and OCSP are accessible via Keychain Access. On the "Certificates" pane in the Preferences of Keychain Access, set the following:
Online Certificate Status Protocol (OCSP): Best Attempt
Certificate Revocation List (CRL): Best Attempt
Priority: OCSP
I wish these Chrome fanboys would go away. Seriously, you infect every thread about a web browser that isn't Chrome. Stop posting off topic.
Chrome is awful btw.
I created a webpage using a simple Javascript loop to loop through the images in a folder all named with numbers in order from 1 to 200 (wedding photos). I opened it in safari. It was "slightly" sluggish, but i was able to go up and down and it was usable. Then i tried opening it in FireFox. Here's where we see a flaw with firefox. The thing froze, and when i opened Activity Monitor, firefox's memory usage was skyrocketing. Conclusion: Firefox can't handle too much at once. Safari and most likely webkit in general seems to be far better at handling huge webpages and in my opinion translates to better design than Gecko. Keep in mind that these photos were done by professionals and as such were fairly high res. I use firefox when I need some functionality that a plugin provides, but for the most part, i stick with Safari. I've tried chrome too, and I like it, but I'm used to safari at this point and I figure that once Lion is out, Safari may very well blow Chrome out of the ballpark with performance and stability thanks to WebKit2, so I'd rather stick with it (Until chrome adopts WebKit2 that is, although that may not happen for some time due to various major design changes).
Chrome = speed, Safari = design.
So if, like me you can't use the MAS after updating to 10.6.7 - SWITCH OFF CRL in the Keychain Prefs and you'll find it works as before! I know its not going to be as secure but you can always switch it on again when you're not using the MAS.
Come on Apple fix this NOW!!
Seriously? am I the only person who hates chrome?
I hate the whole keystone agent stuff that they dot around everywhere, I hate the fact that parts of Google chrome can be found in the right across the system so if you do want to uninstall it it take hours to do it 100% and if you just try deleting the app, application support + preferences files you get a stream of errors in your system log.
The Snow Leopard security update basically revokes Comodo's compromised SSL certificates.
http://support.apple.com/kb/HT4608
The Safari update fixes buffer overflows
http://support.apple.com/kb/HT4596
Fixed this for you..
Chrome = CRASH, Safari = WORKS
Yeah I agree with you, safari is way better than any other browser. Chrome looks like it could be developed more.