Safari Not Opening Pages That Require Login

Question

Since I installed the latest security update Safari won't open a couple of pages I use to use all the time. Most notably the My eBay sign in page and the Bigpond Log In page and just now the Apple Login Page (I had to use Camino to get to here). When I click on these pages Safari just sits there trying to load but does nothing and after about 2min I get the spinning Beachball and have to Force Quit. Also if I press the stop button and try to load any other page other than those 3 it does the same thing. This only happens after I have already clicked on one of the above mentioned sites. I then have to quit Safari and restart it to get it to work. All my other tabbed bookmarks work, It's pretty much just these 3 and probably any other page that requires login.
I have deleted prefs and reset Safari, Repaired Permissions, Deleted Saft, Googled for this problem and found nothing and tried to find a way to reinstall Safari but found nothing.
Anyone got any other ideas.
Thanks

Answer 1

Try this - I was Having the same problems:
http://www.macfixit.com/article.php?story=20061204233133704
"Tuesday, December 05 2006 @ 03:00 AM PST
Security Update 2006-007 (#6): Login to secure sites fails (cont.) -- fixes; Problems launching Microsoft Office apps; more
Login to secure sites fails (cont.) -- fixes We continue to report on problems logging into secure (https) Web sites in Safari and other WebKit-based applications after applying Security Update 2006-007. Since this update makes modifications to WebKit, it's logically implicated in the difficulties.
Even more telling than the WebKit changes, however, is the resolution (in this security update) of a vulnerability where "certain revoked certificates may be erroneously honored." It appears Safari is -- instead of erroneously honoring bad certificates -- erroneously rejecting some certificates.
There's one more change in Security Update 2006-007 that could be implicated in this problem: a fix for a vulnerability where it may be possible to create an X.509 certificate containing a public key that "could consume a significant amount of system resources during signature verification. An attacker may cause a system to process such a certificate, leading to a denial of service."
In at least some cases, the issue appears to be tied to certificates issued by VeriSign. Safari is incorrectly interpreting some of these certificates as invalid -- with a mismatch in the certificate-listed host name and host name of the visited URL.
As such, one potential fix involves deleting certificate entries using Keychain Access, as follows:
1. Launch Keychain Access (located in Applications/Utilities)
2. Click on "Certificates" in the left-hand pane
3. Delete any entries from VeriSign, or any certificates with a red cross next to them
4. Re-attempt access to the problematic secure site
The most successful fix, however, involves deleting the file com.apple.security.revocation.plist from the following directory:
* ~/Library/Preferences
You can replicate this workaround to some extent without deleting any files by opening Keychain Access (as mentioned above) then navigating to its Preferences (under the Keychain Access menu), clicking on the "Certificates" tab and making sure that both "Online Certificate Status Protocol (OCSP)" and "Certificate Revocation List (CRL)" are turned off. However, some users have found that only deleting the aforementioned file works.
Unfortunately, in some cases, it may be up to certificate providers to update their certification methods for compliance with Apple's new, more stringent security standards."