Safari, Firefox, OmniWeb can't log in to online banking after 10.4.9

Question

I too have been having the same problems others have had. I cannot log into my online banking site any more as it crashes each time I do so no matter which browser I use. I tried loggin in with Firefox 2.0.x and with OmniPage 5.0.x, all which crashed!
This is definitely an OS X 10.4.9 problem!!

Answer 1

It is apparently a problem for some users, not all (me included). But you may find this helpful:
Mac OS X 10.4.9 Special Report: Secure site access broken: fixes
Some users are reporting problems with access to secure sites after applying the Mac OS X 10.4.9 update.
Fixes for this issue include:
Replace the X509Anchors file It appears that in some cases, the X509Anchors is not properly installed by the Mac OS X 10.4.9 update, and replacing it with a valid copy can resolve issues with secure site access.
In order to do so, there are two options:
1. Copy the X509Anchors file (which is located in /System/Library/Keychains/ from another system running Mac OS X 10.4.9 that is able to access secure sites back to the system running Mac OS X 10.4.9 that isn't able to access secure sites.
2. Extract the X509Anchors file from the Mac OS X 10.4.9 installer package and place it on your startup volume, replacing the damaged copy via the following instructions:
1. Download the Mac OS X 10.4.9 combo updater appropriate to your system (from Apple's download page).
2. Download and install the shareware application Pacifist
3. Drag the Mac OS X 10.4.9 installer package (e.g. MacOSXUpdCombo10.4.9Intel.pkg) onto the Pacifist application icon.
4. Click the triangle next to "System" to expand it
5. Click the triangle next to "Library" to expand it
6. Click the triangle next to "Keychains" to expand it
7. Scroll down and find the file X509Anchors. Drag it to your Desktop or another location (you will have to enter your administrator password)
8. On your Mac OS X startup drive, navigate to /System/Library/Keychains and locate a similarly named file (X509Anchors). Move it to another location for safe keeping.
9. Now drag the file from step 7 (the one that you retrieved from the Mac OS X 10.4.9 combo install package) into the /System/Library/Keychains, in effect replacing the damaged file with a good copy -- you will have to enter an administrator password.
10. Restart your Mac
Others have had success with this fix:
Delete .plist Delete 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.
[b/Temporarily disabling JavaScript JavaScript can be disabled by opening Safari's preferences (under the "Safari" menu) then clicking the "Security" tab and de-selecting the option "Enable JavaScript."
Empty cache In other cases, this problem can be solved by simply emptying the cache (Safari menu > Empty Cache). In other cases, the solution is to open Safari's preferences, then click on the Security tab, then "Show cookies" and deleting all cookies.
Delete .plist file Some users have found success with deleting the file com.apple.Safari.plist from ~/Library/Preferences.
Reset Safari Finally, resetting Safari (via the "Reset Safari" command, accessible under the "Safari" menu) can resolve site access/login issues in some cases. Note that this will delete your browser history, cache, cookies, and other stored data.
Double-click login.keychain In some cases, the solution is easy as navigating to ~/Library/Keychains/ (this is the Library folder inside your user home folder), then finding the file named "login.keychain" and double-clicking it.