Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

need to avoid error "no common encryption algorithm(s)" "ssl_error_no_cypher_overlap"

  • 15 odgovori
  • 20 ima ovaj problem
  • 3 views
  • Posljednji odgovor poslao John99

more options

How can one put in the right security settings/certificates to make FF work again with all sites? Need to avoid error "no common encryption algorithm(s)" "ssl_error_no_cypher_overlap". Thx.

How can one put in the right security settings/certificates to make FF work again with all sites? Need to avoid error "no common encryption algorithm(s)" "ssl_error_no_cypher_overlap". Thx.

All Replies (15)

more options

You start by updating Firefox from a very old Fx21 to the latest one or the latest one that your XP can support. That may entail upgrading to Fx43 then doing updates from within an open Firefox

What is the Service Pack version of your XP ? If it was fully updated when Microsoft did support it it should be SP3. (For reasons best known to the users, many will use SP2)

more options

Upgrading to latest FF will take away many features of the 80+ plugins...and the layout is also vastly different and even addons cannot fully bring it back. The Chromization is a nightmare, even/especially for a FF-lover!

My XPsp3 is updated to the hilt (and that wrx til 2019), except for what would make virtualization impossible (there was this evil kb from m$ft which tried to kill vm, but it can be uninstalled, hehe).

What's the patchy way to slip-in the right security settings/certificates to make FF work again with all sites (avoiding the error "no common encryption algorithm(s)" or "ssl_error_no_cypher_overlap")?

Thx.

more options

I had found this, but too chicken to check it out.

How to override the Firefox Add-on Signing requirement - g Hacks article https://support.mozilla.org/en-US/forums/support-forum-contributors/712182

more options

John99 said

You start by updating Firefox from a very old Fx21 to the latest one or the latest one that your XP can support. That may entail upgrading to Fx43 then doing updates from within an open Firefox What is the Service Pack version of your XP ? If it was fully updated when Microsoft did support it it should be SP3. (For reasons best known to the users, many will use SP2)

Firefox has required WinXP SP2 at minimum since Firefox 13.0

Starting Firefox 43.0.2 the setups were signed in a way that those still using WinXP SP2 could not run 43.0.2 and later setups however WinXP SP3 users could. WinXP SP2 users could use 43.0.2 and later if they updated internally in Firefox.

https://support.mozilla.org/en-US/kb/get-latest-version-firefox-windows-xp-vista

However I remember seeing a bug report on changing this for Firefox 49.0 so Windows XP users using SP2 and SP3 can install Firefox 49.0 setups now. Also there was a note on Firefox 47 and 48 system requirements pages however it is not on Fx 49.0 page now https://www.mozilla.org/firefox/49.0/system-requirements/

more options

spdgnzls said

Upgrading to latest FF will take away many features of the 80+ plugins...and the layout is also vastly different and even addons cannot fully bring it back. The Chromization is a nightmare, even/especially for a FF-lover!

The appearance change that some thought was looking like it came from Chrome or IE at time on Windows started as of Firefox 29.0

The "Classic Theme Restorer" extension will allow your to make Firefox more like before or even better if you want to change appearance. https://addons.mozilla.org/firefox/addon/classicthemerestorer/

I believe you are referring to Extensions and not Plugins. Extensions requires signing. The Plugins (like Flash PLayer, Java, Silverlight etc) are on system and are not installed in Firefox like Extensions and Themes (complete) are and do not require signing nor are they so Firefox version specific. See https://addons.mozilla.org/faq

You should check to see if there are updates for your Extensions at addons.mozilla.org as you are likely using old versions of Extensions that are three plus years old with the Firefox 21.0 that was released on May 14, 2013

more options

spdgnzls said

What's the patchy way to slip-in the right security settings/certificates to make FF work again with all sites (avoiding the error "no common encryption algorithm(s)" or "ssl_error_no_cypher_overlap")?

A few common reasons to have issues in connecting to https:// sites in Firefox is due to time/date being wrong on OS, using a proxy. The most common reason of late has been due to using a antivirus client that it trying to help you be safe by inserting its own certificate and instead causes problems with connecting to secure sites and people blame Firefox web browser when it was not a problem with Firefox.

https://support.mozilla.org/en-US/kb/troubleshoot-SEC_ERROR_UNKNOWN_ISSUER#w_the-error-occurs-on-multiple-secure-sites

Izmjenjeno od strane James

more options

FredMcD said

I had found this, but too chicken to check it out. How to override the Firefox Add-on Signing requirement - g Hacks article https://support.mozilla.org/en-US/forums/support-forum-contributors/712182

Thx, this is very interesting, I shall check it out (though I need a solution for the security.ssl... to browse websites that otherwise give the error as stated in my initial post of this thread).

more options

Thx for all the info (really appreciate the effort), aware of all of it (but it does not solve the problem).

What you mention: 'SEC_ERROR_UNKNOWN_ISSUER' is not the error.

The ERROR (see subject of thread) is "no common encryption algorithm(s)" "ssl_error_no_cypher_overlap".

Any help re that in order to patch-in/slip-in those missing new security.ssl options, that would be great!

Izmjenjeno od strane spdgnzls

more options

Yes I know the name of the SEC_ERROR_UNKNOWN_ISSUER article may confuse you but the most common reason of various secure connection errors/issues in last year or two have been due to a antivirus client as article is about.

Also the old vulnerable Firefox 21.0 was Released back on May 14, 2013 and there has been a number of changes to vulnerable preferences and settings like with SSL2 and SSL3.

For example SSLv3 was disabled in Firefox 34.0 and later. https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/

IF you are only getting this with a certain website or two then it is a problem with the website in what they support for secure connection. You can check the site at https://www.ssllabs.com/ssltest/

http://forums.mozillazine.org/viewtopic.php?f=38&t=2930597

Izmjenjeno od strane James

more options

Thx, I know that article re that "SEC_ERROR_UNKNOWN_ISSUER", it is a good one.

Of course, I tested it without virus-scanner and firewall, same error as in subject. Does not happen in chrm/dragon (but they are newer with latest security features) but never my choice, FF is best! In the end it is the poorly configured site, over which the browsing user however has no power to change its security settings ;)

The key is to get the latest security settings into FF (even old ones) just as you maintain any other tech. So (I ask again) how can this be done?

more options

What may be worth trying is installing multiple versions of Firefox. That is not going to be an official recommendation that would just have to be saying keep Firefox fully updated. However a lot of the time secure browsing may not be essential, but if you are handling sensitive or personal information or money then it is.

You could use an outdated Firefox for fun surfing but use the secure up to date one when you need the security. We can provide tips on how to do this if it is something you are interested in. Alternatively consider the third party build Firefox portable

That can be used form a memory stick, or installed on a hard drive. You may also be able to get older versions of Firefox portable

more options

Upgraded to FF 38.5.1 ESR, but that is sooo slow with 200 tabs (while FF21 was still fast) that I might just try s/t else. However, at least the protocol problems are gone. In any case, I also tried the Dev Version, and that installs truly separately, but it would have the same problems of speed and adjusting all addons. Considering how powerful computing is these days, browsers should not be so sluggish with many tabs (and they are not even loaded, just URL-populated). But forget Chrome, I'd rather go back to FF21, where everything worked til the protocols broke...and I am sure it can be fixed, but some folks just want their new developments to shine somehow, even if most users suffer from them...

PS: I went back to FF21 with all 80+ addons working and a world of order & speed. Neither v38 nor v45 nor v49 were able to beat FF21, not even close. I do not understand what you guys have been doing since 2013...pls just go back start with something that was good and make it really better (by listening to users, not devs). Don't make the same mistake that monolithic propeller heads make or that big conglomerates have shown (huge design failures and misguided OS devs). Look at OS': anything after xp is crap, except 7, which is somewhat ok (but underneath is all xp), and in 10 you cannot even run old apps anymore (total nono, and that is besides the dozen spxwares build-in).

Izmjenjeno od strane spdgnzls

more options

I note on Mozilla's pages Firefox is claimed to be fast, but those claims are apparently based on Fx19 and outdated blogs.

I know the new multiprocess Firefox is expected to be a game changer. Also unfortunately Firefox is probably the last browser to support XP and probably will discontinue support for XP shortly.

I am not certain it is definite but I did see comments about Fx52 ESR being the last version to support XP. That of course may have little effect on you if you already use old none supported versions of Firefox.

This forum is mainly answered by fellow Firefox users. If you wish to comment where developers may see what you write try the mailing lists|groups

Izmjenjeno od strane John99

more options

Many thx for the insights and links. When looking at the article...I was kinda happy, as their speed tests are (still in 2016) based on FF21 (from 2013), the version I use ;) http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534.html

Could you please run a meaningful survey about what users really want and what has worked for many well (although the latter would point naturally to many addons/extensions, where usage stats exist and hence tell a clear story).

But back to specific problems (these address potential different ways of getting FF21 profile data to a new version, and each way may have benefits, so please try to answer them kinda separately, thx): 1. How can one sync (without cloud, but locally) a FF21 profile into the latest dev 51.0a2 (2016-11-14)? 2. How can one install that version into the FF21 folder as an upgrade? 3. How can one copy the important files (bmrks, pwds, hist, settings, etc) to the above version`? (addendum: pwds done, bmrks failed w export/import)

Many thanks :)

PS: I achieved a more than in FF21 vertically spacious customization of FF51 by using Classic Theme Restorer and Classic Toolbar Buttons as well as Hide Caption Titlebar Plus.

Izmjenjeno od strane spdgnzls

more options

We are just fellow Firefox users here, so we are not going to be running any surveys. Mozilla does however collect telemetry data from those users that agree, and by default from all using some pre-release versions.

1. How can one sync (without cloud, but locally) a FF21 profile into the latest dev 51.0a2 (2016-11-14)?

Firefox Sync is cloud based. However I am not certain all of it will work between widely differing Firefox versions. You could even set up your own local Sync Server, if you want to undertake such a major Project I can provide you with necessary links to the technical articles.

2. How can one install that version into the FF21 folder as an upgrade?

By that I take it you are asking to use a Firefox 21 profile in say Firefox 50. That is pretty easy but not foolproof between widely different versions. You simply overwrite the profile you do not want with a COPY of the profile you wish to use. (Do not move the original profile it could get corrupted) It is IMPORTANT that you copy the content but not the top profile folder name. The name needs to remain what it was when set up in the new version.

3. How can one copy the important files (bmrks, pwds, hist, settings, etc) to the above version`? (addendum: pwds done, bmrks failed w export/import)

This is the method normally used and should work. We have a help article explaining it

Additional Help Articles