
Priorize AES-256
In about:config I filtered for security.ssl3 and disabled all chiper combinations except those 7 ending with _aes_256_sha. Then I tested dozens of of websites and found only one of those I regulary connect to to be not working. That single site insiste on RC4-128. But if I turn on RC4, at least half of all other sites revert to using RC4 instead of AES. I work arround this problem by using a different browser for that problematic website in question, but I'd rather use Firefox as well. Is there a way to enable a specific protocol for a specific website, but not for others?
All Replies (1)
I'm also keeping a lot of ciphers disabled (*.des_ede3_sha are enabled for me) and indeed there are servers that require RC4 ciphers to be enabled to work properly or at all.
Sometimes only CSS files are hosted on such a server and the page looks like no style in such a case.
I have a PrefBar button to toggle some of those prefs easily if necessary.
You can also use a second profile started with the -no-remote switch to run them side-by-side.
See:
- http://kb.mozillazine.org/Creating_a_new_Firefox_profile_on_Windows
- http://kb.mozillazine.org/Shortcut_to_a_specific_profile
- http://kb.mozillazine.org/Using_multiple_profiles_-_Firefox
You can use the -no-remote command line switch to open another Firefox instance with its own profile and run multiple Firefox instances simultaneously.