I have been using Firefox for years and have had no issue. Tonight, when I try to go to my normal websites (AOL mail, Etsy, etc.) I receive an error message of:
This Connection is Untrusted
You have asked Firefox to connect securely to my.screenname.aol.com, but we can’t confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site’s identity can’t be verified.
What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn’t continue.
my.screenname.aol.com uses an invalid security certificate.
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
(Error code: sec_error_cert_signature_algorithm_disabled)
I have tried updating Firefox, I have run a security check, I have search the forums…I have not found a solution for this error code.
What am I able to do?
I have been using Firefox for years and have had no issue. Tonight, when I try to go to my normal websites (AOL mail, Etsy, etc.) I receive an error message of:
This Connection is Untrusted
You have asked Firefox to connect securely to my.screenname.aol.com, but we can’t confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site’s identity can’t be verified.
What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn’t continue.
my.screenname.aol.com uses an invalid security certificate.
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
(Error code: sec_error_cert_signature_algorithm_disabled)
I have tried updating Firefox, I have run a security check, I have search the forums…I have not found a solution for this error code.
What am I able to do?
Chosen solution
All Replies (13)
Try to rename the cert8.db file (cert8.db.old) and delete the cert_override.txt file in the Firefox profile folder to remove intermediate certificates and exceptions that Firefox has stored.
If that has helped to solve the problem then you can remove the renamed cert8.db.old file.
Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previously stored intermediate certificates.
Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.
You can use this button to go to the current Firefox profile folder:
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
I thank you for your time and efforts. I tried the suggestion and renamed the cert file and deleted the cert override file and I am still receiving the same error message.
Hmm, when I look at the cert on that site it seems fine. (Screen shot attached.)
On Etsy and other secure sites, is it that same code: «sec_error_cert_signature_algorithm_disabled»?
Could you take a look at your preference settings and see whether any of these have been modified from their defaults:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste security.ssl and pause while the list is filtered
(3) If any preferences starting with security.ssl are bolded and «user set» to false, you can right-click > Copy Name and paste it into a reply here for consideration.
Note: it’s okay to set these two to false (note they have dhe in them):
- security.ssl3.dhe_rsa_aes_128_sha
- security.ssl3.dhe_rsa_aes_256_sha
Below are all of the items that came up false:
security.ssl.errorReporting.automatic
security.ssl.false_start.require-npn
security.ssl.require_safe_negotiation
security.ssl.treat_unsafe_negotiation_as_broken
The items were not is bold and were labeled as default, but I included them anyway.
Thanks!
What are the settings of the above mentioned ‘security.ssl3.dhe’ prefs?
You can set these prefs to false on the about:config page to disable the cipher suites that are involved with the Logjam vulnerability in case they are currently enabled.
- security.ssl3.dhe_rsa_aes_128_sha
- security.ssl3.dhe_rsa_aes_256_sha
security.ssl3.dhe_rsa_aes_128_sha;true
security.ssl3.dhe_rsa_aes_256_sha;true
I tried to change the two above mentioned items and I received the same error code. It originally let me on AOL mail this morning, for about a minute and a half, but then I received the same error message as in the original post. This is the same error message that I receive through the Etsy site also.
Two other users just posted about getting this «sec_error_cert_signature_algorithm_disabled» error, which otherwise is very rare on this forum. Perhaps there is some new malware going around, or a change in Firefox surfaced an issue with something that was already on your system.
Have you ever seen this code on any other secure site?
Actually, you already mentioned two sites, so probably there are more.
To gather further information, you could inspect a sample certificate to see whether that points to the culprit. For example, you can open my test page at:
https://jeffersonscher.com/res/jstest.php
You likely will get an error page. Expand the «I understand the risks» section and look for an Add Exception button.
Note: You don’t need to complete the process of adding an exception — I suggest not adding one until we know this isn’t a malware issue — but you can use the dialog to view the information that makes Firefox suspicious.
Click Add Exception, and the certificate exception dialog should open.
Click the View button. If View is not enabled, try the Get Certificate button first.
This should pop up the Certificate Viewer. Look at the «Issued by» section, and on the Details tab, the Certificate Hierarchy. What do you see there? I have attached a screen shot for comparison.
I have attached images of what your steps showed.
As mentioned by cor-el, check for a program or add-on named E-Rewards and/or E-Rewards Notify.
(1) Open the Windows Control Panel, Uninstall a Program. After the list loads, click the «Installed on» column heading to group the infections, I mean, additions, by date. This can help in smoking out undisclosed bundle items that snuck in with some software you agreed to install. Be suspicious of everything you do not recognize/remember, as malware often uses important or innocent sounding names to discourage you from removing it. Take out as much trash as possible here.
(2) Open Firefox’s Add-ons page using either:
- Ctrl+Shift+a
- «3-bar» menu button (or Tools menu) > Add-ons
- in the Windows «Run» dialog, type or paste
firefox.exe "about:addons"
In the left column, click Plugins. Set nonessential and unrecognized plugins to «Never Activate».
In the left column, click Extensions. Then, if in doubt, disable (or Remove, if possible) unrecognized and unwanted extensions. Bear in mind that all extensions are optional, none come with Firefox, and you can learn more about them by checking their reviews on the Add-ons site.
Often a link will appear above at least one disabled extension to restart Firefox. You can complete your work on the tab and click one of the links as the last step.
Does that resolve it? If not:
(3) You can search for remaining issues with the scanning/cleaning tools listed in our support article: Troubleshoot Firefox issues caused by malware. These on-demand scanners are free and take considerable time to run. If they finish quickly and especially if they require payment, you may have a serious infection. I suggest the specialized forums listed in the article in that case.
Success?
Thank You! I went through your steps and followed the link from another user having the same issue. I had the e-rewards notify app and have uninstalled it. The issue seem to have been resolved, at least for now.
Some users are seeing the Error Code: sec_error_cert_signature_algorithm_disabled when trying to visit certain websites from their FireFox browser. Most affected users report that the issue started occurring abruptly – prior to this, the web pages could be visited without issues. The issue is reported to occur on both Windows and Mac computers.
What is causing the ‘sec_error_cert_signature_algorithm_disabled’ error?
We investigated this particular issue by looking at various user reports and the repair strategies that most affected users have operated in order to resolve the issue. Based on what we gathered, there are several common culprits that are known to trigger this particular error:
- Intermediate certificate and exceptions are causing the error – Several affected users have managed to resolve the issue by editing the Firefox profile folder to disregard certificates and exceptions that might be causing the issue. The easiest way to do this is by deleting the cert_override.txt and editing the cert9.db or cert8.db file.
- Adware app is causing the security prompt – E-rewards Notify App and a few other applications that serve as fronts for adware can also trigger this error message. Tracking them down and uninstalling them from your system will resolve the issue if this scenario is applicable.
- Malware infection – As it turns out, browser hijackers are also confirmed to trigger this particular error message. In this case, using a specialized security scanner to remove the malware infection and reinstalling Firefox should resolve the issue.
- HTTPS filtering is enabled on Avast – Avast has a long history of throwing false positives with Firefox because of its habit of sending out IIRC connection details. In this case, disabling HTTPS scanning should stop the false positives from appearing again.
- Kaspersky Root Antivirus certificate is not installed on Firefox – If you’re using a 64-bit version of FireFox in conjunction with Kaspersky, chances are the issue is occurring because your Firefox installation is missing the antivirus root certificate. A quick trip to the Certificates menu should resolve the issue in this case.
If you’re currently struggling to resolve this Firefox issue, this article will provide you with several troubleshooting steps that other users in a similar position successfully used to get the issue fixed. The methods below are ordered by efficiency and severity, so please follow them in order until you stumble upon a fix that resolves the issue in your case.
Method 1: Renaming cert.db & deleting cert_override.txt
Several affected users have reported that the issue was resolved after they renamed the cert8.db or cert9.db file and deleting the cert_override.txt file from the Firefox profile folder. This operation will remove intermediate certificates and exceptions that Firefox currently stores, which should, in turn, resolve the sec_error_cert_signature_algorithm_disabled error.
Here’s a quick guide on how to do this:
- Open Firefox and click the Action button in the top-right corner of the screen. Then, click on Help, and choose Troubleshooting Information from the newly appeared menu.
- From the Troubleshooting Information screen, click the Open Folder button associated with the Profile folder.
- Once you’re inside you’re current Firefox Profile, go ahead and close the FireFox application so that we can operate the changes.
- Once Firefox is closed, right-click on cert9.db or cert8.db (depending on the Firefox version that you installed) and choose Rename. Next, add a ‘.old‘ after the ‘.db’ extension and hit Enter to save your changes. This will instruct the browser to disregard the current Database file and create a new one at the next startup.
Note: If you can’t see the extension of your files in File Explorer, go to the View tab (using the ribbon bar at the top) and make sure that the box associated with Hidden Items is checked. - Then, right-click on the cert_override.txt and choose Delete to remove any intermediate certificates and exceptions that FireFox is currently storing.
- Once these two changes have been made, restart your Firefox browser and see if you’re still encountering the sec_error_cert_signature_algorithm_disabled error.
If you’re still seeing the same error message, move down to the next method below.
Method 2: Uninstalling the Adware app
There are several malware/adware products that are known to trigger this particular error message. While there are certainly other variations of this, the E-Rewards Notify App is by far the most commonly reported culprit when it comes to the sec_error_cert_signature_algorithm_disabled error.
Several affected users have reported that the issue was resolved after they used the Programs and Features window to uninstall the adware that is producing the error. Here’s a quick guide on how to do this:
- Press Windows key + R to open up a Run dialog box. Then, type “appwiz.cpl” and press Enter to open up the Programs and Features list.
Type appwiz.cpl and Press Enter to Open Installed Programs List - Once you get inside the Programs and Features window, skim through the list and see if you can find a suspicious program that might have been used as a front o install adware. Obviously, you should start looking for the E-Rewards Notify App since it’s the most popular adware variation known to produce this particular error.
Note: It might help to via Installed On if you have a general idea when the issue started occurring. - Once you see it, right-click on it and choose Uninstall. Then, follow the on-screen prompts to complete the uninstallation.
Uninstalling the adware application - Once the uninstallation is complete, restart your computer.
- At the next startup, see if the issue has been resolved by visiting the same webpages that we’re previously triggering the sec_error_cert_signature_algorithm_disabled error.
If you’re still seeing the same error message, move down to the next method below.
Method 3: Performing a malware scan
If you weren’t able to pinpoint and eliminate the adware/malware that was causing the issue, using a security scanner to identify the culprit is about your only choice by now. Several affected users have reported that a malware scan identified and eliminated a nasty browser hijacker.
Based on our personal experience, there are few better free security scanners capable of dealing with browser hijackers than Malwarebytes. To eliminate the possibility of a malware/adware causing the sec_error_cert_signature_algorithm_disabled error, follow this article (here) to initiate a deep scan with Malwarebytes.
Once the scan is complete, restart your computer and reinstall your Firefox browser at the next startup. This step is necessary because, in the event of a browser hijacker, some infected browser files will have been deleted in the cleaning process.
Method 4: Disabling HTTPS filtering (Avast only)
As some users have reported, this particular issue can also occur if you’re using Avast! antivirus. Turns out that in some scenarios, Avast! might trigger a false positive thinking a MITM (man in the middle) is underway on your computer.
We investigated this possibility thoroughly and it turns out that AVAST! is notorious for sending out details of your connections (IIRC), which ends up triggering the sec_error_cert_signature_algorithm_disabled error in Firefox.
If this scenario is applicable to your current situation, you will be able to deal with the false positive by opening your Avast Settings, going to Main settings and ensuring that the checkbox associated with Enable HTTPS scanning is disabled.
Once the change has been operated, restart your computer and see if the issue has been resolved.
If this particular method wasn’t applicable, move down to the next method below.
Method 5: Manually Install Kaspersky’s antivirus root certificate in Firefox
If you’re using a 64-bit version of FireFox with Kaspersky, the sec_error_cert_signature_algorithm_disabled error might occur because your Firefox installation is missing the antivirus root certificate.
Here’s a quick guide on fixing the issue if this scenario is applicable:
- Open Firefox, click the action button (top-right) corner, then click on Options.
- Inside the Options tab, click the Privacy & Security tab from the left-hand menu, then scroll down to Certificates and click on View Certificates.
Viewing Certificates in Firefox - Then, inside the Certificate Manager, click on the Authorities tab and click the Import menu.
Importing the certificate - Once you get to the import menu, paste the following location inside the address bar and press Enter. Then, select the Root Certificate from that folder and click Open.
Importing the Personal Root Certificate - At the confirmation window, make sure that all trust boxes are enabled before clicking Ok.
- Restart your browser and check if the issue has been resolved.
If you’re still encountering the sec_error_cert_signature_algorithm_disabled error, move down to the next method below.
Method 6: Adjusting the security.pki.sha1_enforcement_level value
Some affected users that had issues with accessing Facebook Workspace and a few other similar services have reported that the issue was resolved after they accessed the advanced settings of firefox and adjusted the Security Enforcement Level value.
This procedure will reconfigure your Firefox browser to accept SHA-1 certificates without any further checkups, which will end up eliminating the issue. However, going this route might leave your browsing sessions open to security attacks.
If you decide to go this route, here’s what you need to do:
- Open Firefox, type ‘about:config‘ in the navigation bar and press Enter to access the advanced settings.
- At the security prompt, click the I accept the risk! button.
- Once you’re inside the advanced settings of Firefox, type “security.pki.sha1” in the search box to locate the value that needs to be modified.
- Next, double click on security.pki.sha1_enforcement_level;3 and change it’s value to 4 before clicking Ok.
- Restart your browser and see if the issue has been resolved.
Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.
Содержание
- Fix: Sec_Error_Cert_Signature_Algorithm_Disabled
- What is causing the ‘sec_error_cert_signature_algorithm_disabled’ error?
- Method 1: Renaming cert.db & deleting cert_override.txt
- Method 2: Uninstalling the Adware app
- Method 3: Performing a malware scan
- Method 4: Disabling HTTPS filtering (Avast only)
- Method 5: Manually Install Kaspersky’s antivirus root certificate in Firefox
- Method 6: Adjusting the security.pki.sha1_enforcement_level value
- Sec error cert signature algorithm disabled
- Chosen solution
- All Replies (13)
- Chosen Solution
Fix: Sec_Error_Cert_Signature_Algorithm_Disabled
Some users are seeing the Error Code: sec_error_cert_signature_algorithm_disabled when trying to visit certain websites from their FireFox browser. Most affected users report that the issue started occurring abruptly – prior to this, the web pages could be visited without issues. The issue is reported to occur on both Windows and Mac computers.
Error Code: sec_error_cert_signature_algorithm_disabled
What is causing the ‘sec_error_cert_signature_algorithm_disabled’ error?
We investigated this particular issue by looking at various user reports and the repair strategies that most affected users have operated in order to resolve the issue. Based on what we gathered, there are several common culprits that are known to trigger this particular error:
- Intermediate certificate and exceptions are causing the error – Several affected users have managed to resolve the issue by editing the Firefox profile folder to disregard certificates and exceptions that might be causing the issue. The easiest way to do this is by deleting the cert_override.txt and editing the cert9.db or cert8.db file.
- Adware app is causing the security prompt – E-rewards Notify App and a few other applications that serve as fronts for adware can also trigger this error message. Tracking them down and uninstalling them from your system will resolve the issue if this scenario is applicable.
- Malware infection – As it turns out, browser hijackers are also confirmed to trigger this particular error message. In this case, using a specialized security scanner to remove the malware infection and reinstalling Firefox should resolve the issue.
- HTTPS filtering is enabled on Avast – Avast has a long history of throwing false positives with Firefox because of its habit of sending out IIRC connection details. In this case, disabling HTTPS scanning should stop the false positives from appearing again.
- Kaspersky Root Antivirus certificate is not installed on Firefox – If you’re using a 64-bit version of FireFox in conjunction with Kaspersky, chances are the issue is occurring because your Firefox installation is missing the antivirus root certificate. A quick trip to the Certificates menu should resolve the issue in this case.
If you’re currently struggling to resolve this Firefox issue, this article will provide you with several troubleshooting steps that other users in a similar position successfully used to get the issue fixed. The methods below are ordered by efficiency and severity, so please follow them in order until you stumble upon a fix that resolves the issue in your case.
Method 1: Renaming cert.db & deleting cert_override.txt
Several affected users have reported that the issue was resolved after they renamed the cert8.db or cert9.db file and deleting the cert_override.txt file from the Firefox profile folder. This operation will remove intermediate certificates and exceptions that Firefox currently stores, which should, in turn, resolve the sec_error_cert_signature_algorithm_disabled error.
Here’s a quick guide on how to do this:
- Open Firefox and click the Action button in the top-right corner of the screen. Then, click on Help, and choose Troubleshooting Information from the newly appeared menu.
- From the Troubleshooting Information screen, click the Open Folder button associated with the Profile folder.
- Once you’re inside you’re current Firefox Profile, go ahead and close the FireFox application so that we can operate the changes.
- Once Firefox is closed, right-click on cert9.db or cert8.db (depending on the Firefox version that you installed) and choose Rename. Next, add a ‘.old‘ after the ‘.db’ extension and hit Enter to save your changes. This will instruct the browser to disregard the current Database file and create a new one at the next startup.
Note: If you can’t see the extension of your files in File Explorer, go to the View tab (using the ribbon bar at the top) and make sure that the box associated with Hidden Items is checked. - Then, right-click on the cert_override.txt and choose Delete to remove any intermediate certificates and exceptions that FireFox is currently storing.
- Once these two changes have been made, restart your Firefox browser and see if you’re still encountering the sec_error_cert_signature_algorithm_disabled error.
Renaming cert.db & deleting cert_override.txt
If you’re still seeing the same error message, move down to the next method below.
Method 2: Uninstalling the Adware app
There are several malware/adware products that are known to trigger this particular error message. While there are certainly other variations of this, the E-Rewards Notify App is by far the most commonly reported culprit when it comes to the sec_error_cert_signature_algorithm_disabled error.
Several affected users have reported that the issue was resolved after they used the Programs and Features window to uninstall the adware that is producing the error. Here’s a quick guide on how to do this:
- Press Windows key + R to open up a Run dialog box. Then, type “appwiz.cpl” and press Enter to open up the Programs and Features list.
Type appwiz.cpl and Press Enter to Open Installed Programs List
- Once you get inside the Programs and Features window, skim through the list and see if you can find a suspicious program that might have been used as a front o install adware. Obviously, you should start looking for the E-Rewards Notify App since it’s the most popular adware variation known to produce this particular error.
Note: It might help to via Installed On if you have a general idea when the issue started occurring. - Once you see it, right-click on it and choose Uninstall. Then, follow the on-screen prompts to complete the uninstallation.
Uninstalling the adware application
- Once the uninstallation is complete, restart your computer.
- At the next startup, see if the issue has been resolved by visiting the same webpages that we’re previously triggering the sec_error_cert_signature_algorithm_disabled error.
If you’re still seeing the same error message, move down to the next method below.
Method 3: Performing a malware scan
If you weren’t able to pinpoint and eliminate the adware/malware that was causing the issue, using a security scanner to identify the culprit is about your only choice by now. Several affected users have reported that a malware scan identified and eliminated a nasty browser hijacker.
Based on our personal experience, there are few better free security scanners capable of dealing with browser hijackers than Malwarebytes. To eliminate the possibility of a malware/adware causing the sec_error_cert_signature_algorithm_disabled error, follow this article (here) to initiate a deep scan with Malwarebytes.
Once the scan is complete, restart your computer and reinstall your Firefox browser at the next startup. This step is necessary because, in the event of a browser hijacker, some infected browser files will have been deleted in the cleaning process.
Method 4: Disabling HTTPS filtering (Avast only)
As some users have reported, this particular issue can also occur if you’re using Avast! antivirus. Turns out that in some scenarios, Avast! might trigger a false positive thinking a MITM (man in the middle) is underway on your computer.
We investigated this possibility thoroughly and it turns out that AVAST! is notorious for sending out details of your connections (IIRC), which ends up triggering the sec_error_cert_signature_algorithm_disabled error in Firefox.
If this scenario is applicable to your current situation, you will be able to deal with the false positive by opening your Avast Settings, going to Main settings and ensuring that the checkbox associated with Enable HTTPS scanning is disabled. Once the change has been operated, restart your computer and see if the issue has been resolved.
If this particular method wasn’t applicable, move down to the next method below.
Method 5: Manually Install Kaspersky’s antivirus root certificate in Firefox
If you’re using a 64-bit version of FireFox with Kaspersky, the sec_error_cert_signature_algorithm_disabled error might occur because your Firefox installation is missing the antivirus root certificate.
Here’s a quick guide on fixing the issue if this scenario is applicable:
- Open Firefox, click the action button (top-right) corner, then click on Options.
- Inside the Options tab, click the Privacy & Security tab from the left-hand menu, then scroll down to Certificates and click on View Certificates.
Viewing Certificates in Firefox
- Then, inside the Certificate Manager, click on the Authorities tab and click the Import menu.
Importing the certificate
- Once you get to the import menu, paste the following location inside the address bar and press Enter. Then, select the Root Certificate from that folder and click Open.
Importing the Personal Root Certificate
If you’re still encountering the sec_error_cert_signature_algorithm_disabled error, move down to the next method below.
Method 6: Adjusting the security.pki.sha1_enforcement_level value
Some affected users that had issues with accessing Facebook Workspace and a few other similar services have reported that the issue was resolved after they accessed the advanced settings of firefox and adjusted the Security Enforcement Level value.
This procedure will reconfigure your Firefox browser to accept SHA-1 certificates without any further checkups, which will end up eliminating the issue. However, going this route might leave your browsing sessions open to security attacks.
If you decide to go this route, here’s what you need to do:
- Open Firefox, type ‘about:config‘ in the navigation bar and press Enter to access the advanced settings.
- At the security prompt, click the I accept the risk! button.
- Once you’re inside the advanced settings of Firefox, type “security.pki.sha1” in the search box to locate the value that needs to be modified.
- Next, double click on security.pki.sha1_enforcement_level;3 and change it’s value to 4 before clicking Ok.
- Restart your browser and see if the issue has been resolved.
Adjusting the Security PKI SHA-1 value
Источник
Sec error cert signature algorithm disabled
I have been using Firefox for years and have had no issue. Tonight, when I try to go to my normal websites (AOL mail, Etsy, etc.) I receive an error message of:
This Connection is Untrusted
You have asked Firefox to connect securely to my.screenname.aol.com, but we can’t confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site’s identity can’t be verified.
What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn’t continue.
my.screenname.aol.com uses an invalid security certificate.
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
(Error code: sec_error_cert_signature_algorithm_disabled)
I have tried updating Firefox, I have run a security check, I have search the forums. I have not found a solution for this error code.
What am I able to do?
Chosen solution
- [/questions/936029] All https: websites are experiencing cert untrusted errors with Digitalmarketresearchapps Pty Ltd showing as cert provider. No viruses detected on my system.
Try to rename the cert8.db file (cert8.db.old) and delete the cert_override.txt file in the Firefox profile folder to remove intermediate certificates and exceptions that Firefox has stored.
If that has helped to solve the problem then you can remove the renamed cert8.db.old file. Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previously stored intermediate certificates. Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.
You can use this button to go to the current Firefox profile folder:
- Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
- http://kb.mozillazine.org/Profile_folder_-_Firefox
I thank you for your time and efforts. I tried the suggestion and renamed the cert file and deleted the cert override file and I am still receiving the same error message.
Hmm, when I look at the cert on that site it seems fine. (Screen shot attached.)
On Etsy and other secure sites, is it that same code: «sec_error_cert_signature_algorithm_disabled»?
Could you take a look at your preference settings and see whether any of these have been modified from their defaults:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste security.ssl and pause while the list is filtered
(3) If any preferences starting with security.ssl are bolded and «user set» to false, you can right-click > Copy Name and paste it into a reply here for consideration.
Note: it’s okay to set these two to false (note they have dhe in them):
- security.ssl3.dhe_rsa_aes_128_sha
- security.ssl3.dhe_rsa_aes_256_sha
Below are all of the items that came up false:
security.ssl.errorReporting.automatic security.ssl.false_start.require-npn security.ssl.require_safe_negotiation security.ssl.treat_unsafe_negotiation_as_broken
The items were not is bold and were labeled as default, but I included them anyway.
What are the settings of the above mentioned ‘security.ssl3.dhe’ prefs?
You can set these prefs to false on the about:config page to disable the cipher suites that are involved with the Logjam vulnerability in case they are currently enabled.
I tried to change the two above mentioned items and I received the same error code. It originally let me on AOL mail this morning, for about a minute and a half, but then I received the same error message as in the original post. This is the same error message that I receive through the Etsy site also.
Two other users just posted about getting this «sec_error_cert_signature_algorithm_disabled» error, which otherwise is very rare on this forum. Perhaps there is some new malware going around, or a change in Firefox surfaced an issue with something that was already on your system.
Have you ever seen this code on any other secure site?
Actually, you already mentioned two sites, so probably there are more.
To gather further information, you could inspect a sample certificate to see whether that points to the culprit. For example, you can open my test page at:
You likely will get an error page. Expand the «I understand the risks» section and look for an Add Exception button.
Note: You don’t need to complete the process of adding an exception — I suggest not adding one until we know this isn’t a malware issue — but you can use the dialog to view the information that makes Firefox suspicious.
Click Add Exception, and the certificate exception dialog should open.
Click the View button. If View is not enabled, try the Get Certificate button first.
This should pop up the Certificate Viewer. Look at the «Issued by» section, and on the Details tab, the Certificate Hierarchy. What do you see there? I have attached a screen shot for comparison.
I have attached images of what your steps showed.
Maybe check in another browser like Google Chrome what certificate(s) are used and other connection details like the TLS version.
You can check the connection settings.
If you do not need to use a proxy to connect to internet then try to select «No Proxy» if «Use the system proxy settings» or one of the others do not work properly.
See «Firefox connection settings»:
Chosen Solution
- [/questions/936029] All https: websites are experiencing cert untrusted errors with Digitalmarketresearchapps Pty Ltd showing as cert provider. No viruses detected on my system.
Modified January 1, 2016 at 3:10:06 PM PST by cor-el
As mentioned by cor-el, check for a program or add-on named E-Rewards and/or E-Rewards Notify.
(1) Open the Windows Control Panel, Uninstall a Program. After the list loads, click the «Installed on» column heading to group the infections, I mean, additions, by date. This can help in smoking out undisclosed bundle items that snuck in with some software you agreed to install. Be suspicious of everything you do not recognize/remember, as malware often uses important or innocent sounding names to discourage you from removing it. Take out as much trash as possible here.
(2) Open Firefox’s Add-ons page using either:
- Ctrl+Shift+a
- «3-bar» menu button (or Tools menu) > Add-ons
- in the Windows «Run» dialog, type or paste
firefox.exe «about:addons»
In the left column, click Plugins. Set nonessential and unrecognized plugins to «Never Activate».
In the left column, click Extensions. Then, if in doubt, disable (or Remove, if possible) unrecognized and unwanted extensions. Bear in mind that all extensions are optional, none come with Firefox, and you can learn more about them by checking their reviews on the Add-ons site.
Often a link will appear above at least one disabled extension to restart Firefox. You can complete your work on the tab and click one of the links as the last step.
Does that resolve it? If not:
(3) You can search for remaining issues with the scanning/cleaning tools listed in our support article: Troubleshoot Firefox issues caused by malware. These on-demand scanners are free and take considerable time to run. If they finish quickly and especially if they require payment, you may have a serious infection. I suggest the specialized forums listed in the article in that case.
Источник
Некоторые пользователи видят Код ошибки: sec_error_cert_signature_algorithm_disabled при попытке посетить определенные веб-сайты из браузера FireFox. Большинство затронутых пользователей сообщают, что проблема стала возникать внезапно — до этого веб-страницы можно было посещать без проблем. Сообщается, что проблема возникает как на компьютерах Windows, так и на Mac.
Что вызывает «sec_error_cert_signature_algorithm_disabled ’ошибка?
Мы исследовали эту конкретную проблему, изучив различные отчеты пользователей и стратегии восстановления, которые использовались наиболее пострадавшими пользователями для ее решения. Исходя из того, что мы собрали, существует несколько распространенных виновников, которые вызывают именно эту ошибку:
- Промежуточный сертификат и исключения вызывают ошибку — Нескольким затронутым пользователям удалось решить проблему, отредактировав папку профиля Firefox, чтобы игнорировать сертификаты и исключения, которые могли вызывать проблему. Самый простой способ сделать это — удалить cert_override.txt и отредактировать файл cert9.db или cert8.db.
- Рекламное приложение вызывает запрос безопасности — Приложение E-rewards Notify и несколько других приложений, которые служат прикрытием для рекламного ПО, также могут вызывать это сообщение об ошибке. Их отслеживание и удаление из вашей системы решит проблему, если этот сценарий применим.
- Заражение вредоносным ПО — Как оказалось, угонщики браузера также могут вызывать именно это сообщение об ошибке. В этом случае использование специализированного сканера безопасности для удаления заражения вредоносным ПО и переустановка Firefox должны решить проблему.
- Фильтрация HTTPS включена в Avast — Avast имеет долгую историю ложных срабатываний Firefox из-за своей привычки отправлять данные соединения IIRC. В этом случае отключение сканирования HTTPS должно остановить повторное появление ложных срабатываний.
- Сертификат Kaspersky Root Antivirus не установлен в Firefox — Если вы используете 64-битную версию FireFox вместе с Kaspersky, скорее всего, проблема возникает из-за того, что в вашей установке Firefox отсутствует корневой сертификат антивируса. Быстрый переход в меню Сертификаты должен решить проблему в этом случае.
Если вы в настоящее время пытаетесь решить эту проблему с Firefox, эта статья предоставит вам несколько шагов по устранению неполадок, которые другие пользователи в аналогичной должности успешно использовали для решения проблемы. Приведенные ниже методы упорядочены по эффективности и серьезности, поэтому, пожалуйста, следуйте им по порядку, пока не наткнетесь на исправление, решающее проблему в вашем случае.
Метод 1: переименование cert.db и удаление cert_override.txt
Несколько затронутых пользователей сообщили, что проблема была решена после того, как они переименовали cert8.db или cert9.db файл и удаление cert_override.txt файл из папки профиля Firefox. Эта операция удалит промежуточные сертификаты и исключения, которые Firefox в настоящее время хранит, что, в свою очередь, должно разрешить sec_error_cert_signature_algorithm_disabled ошибка.
Вот краткое руководство, как это сделать:
- Откройте Firefox и щелкните значок Действие в правом верхнем углу экрана. Затем нажмите на Помогите, и выберите Информация об устранении неполадок из недавно появившегося меню.
- На экране информации об устранении неполадок щелкните значок Открыть папку кнопка, связанная с Профиль папка.
- Как только вы войдете в свой текущий профиль Firefox, закройте приложение FireFox, чтобы мы могли внести изменения.
- После закрытия Firefox щелкните правой кнопкой мыши cert9.db или cert8.db (в зависимости от установленной вами версии Firefox) и выберите Переименовать. Затем добавьте «.old‘После расширения‘ .db ’и нажмите Войти чтобы сохранить изменения. Это укажет браузеру игнорировать текущий файл базы данных и создать новый при следующем запуске.
Примечание: Если вы не видите расширения файлов в проводнике, перейдите в Посмотреть вкладка (используя полосу ленты вверху) и убедитесь, что поле, связанное с Скрытые предметы проверено. - Затем щелкните правой кнопкой мыши значок cert_override.txt и выберите Удалить чтобы удалить любые промежуточные сертификаты и исключения, которые FireFox в настоящее время хранит.
- После того, как эти два изменения будут внесены, перезапустите браузер Firefox и посмотрите, продолжает ли вы сталкиваться с sec_error_cert_signature_algorithm_disabled ошибка.
Если вы по-прежнему видите то же сообщение об ошибке, перейдите к следующему способу ниже.
Метод 2: удаление приложения Adware
Известно, что существует несколько вредоносных / рекламных продуктов, которые вызывают это конкретное сообщение об ошибке. Хотя, безусловно, есть и другие варианты этого, Приложение E-Rewards Notify на сегодняшний день является наиболее частым виновником, когда дело доходит до sec_error_cert_signature_algorithm_disabled ошибка.
Несколько затронутых пользователей сообщили, что проблема была решена после того, как они использовали Программы и особенности окно для удаления рекламного ПО, вызывающего ошибку. Вот краткое руководство, как это сделать:
- Нажмите Клавиша Windows + R , чтобы открыть диалоговое окно «Выполнить». Затем введите «Appwiz.cpl» и нажмите Войти открыть Программы и особенности список.
- Как только вы попадете внутрь Программы и особенности Просмотрите список и посмотрите, сможете ли вы найти подозрительную программу, которая могла быть использована в качестве переднего плана для установки рекламного ПО. Очевидно, вам следует начать искать Приложение E-Rewards Notify поскольку это самый популярный вариант рекламного ПО, вызывающий именно эту ошибку.
Примечание: Это может помочь через Установлено на если у вас есть общее представление о том, когда возникла проблема. - Увидев его, щелкните его правой кнопкой мыши и выберите Удалить. Затем следуйте инструкциям на экране, чтобы завершить удаление.
- После завершения удаления перезагрузите компьютер.
- При следующем запуске проверьте, была ли решена проблема, посетив те же веб-страницы, на которых мы ранее запускали sec_error_cert_signature_algorithm_disabled ошибка.
Если вы по-прежнему видите то же сообщение об ошибке, перейдите к следующему способу ниже.
Метод 3. Выполнение сканирования на наличие вредоносных программ
Если вам не удалось точно определить и устранить рекламное ПО или вредоносное ПО, которое вызывало проблему, использование сканера безопасности для определения виновника — ваш единственный выбор. Несколько затронутых пользователей сообщили, что сканирование на вредоносное ПО выявило и устранило неприятного угонщика браузера.
Исходя из нашего личного опыта, существует несколько лучших бесплатных сканеров безопасности, способных бороться с угонщиками браузера, чем Malwarebytes. Чтобы исключить возможность вредоносного / рекламного ПО, вызывающего sec_error_cert_signature_algorithm_disabled ошибка, следуйте этой статье (Вот), чтобы запустить глубокое сканирование с помощью Malwarebytes.
После завершения сканирования перезагрузите компьютер и переустановите браузер Firefox при следующем запуске. Этот шаг необходим, потому что в случае взлома браузера некоторые зараженные файлы браузера будут удалены в процессе очистки.
Способ 4. Отключение фильтрации HTTPS (только Avast)
Как сообщают некоторые пользователи, эта конкретная проблема также может возникнуть, если вы используете Avast! антивирус. Оказывается, в некоторых случаях Avast! может вызвать ложное срабатывание, если на вашем компьютере выполняется MITM (человек в центре).
Мы тщательно изучили эту возможность, и оказалось, что AVAST! печально известен рассылкой деталей ваших подключений (IIRC), что в конечном итоге вызывает sec_error_cert_signature_algorithm_disabled ошибка в Firefox.
Если этот сценарий применим к вашей текущей ситуации, вы сможете справиться с ложным срабатыванием, открыв настройки Avast и выбрав Основные параметры и убедитесь, что флажок, связанный с Включить сканирование HTTPS выключен.После внесения изменений перезагрузите компьютер и посмотрите, решена ли проблема.
Если этот конкретный метод не применим, перейдите к следующему способу ниже.
Метод 5: вручную установить корневой сертификат антивируса Касперского в Firefox
Если вы используете 64-битную версию FireFox с Kaspersky, sec_error_cert_signature_algorithm_disabled ошибка может возникнуть из-за того, что в вашей установке Firefox отсутствует корневой сертификат антивируса.
Вот краткое руководство по устранению проблемы, если этот сценарий применим:
- Откройте Firefox, нажмите кнопку действия (верхний правый) угол, затем нажмите Параметры.
- Внутри Параметры перейдите на вкладку Конфиденциальность и безопасность в левом меню, затем прокрутите вниз до Сертификаты и нажмите на Посмотреть сертификаты.
- Затем внутри Диспетчер сертификатов, нажми на Органы власти вкладку и щелкните Импортировать меню.
- Как только вы попадете в меню импорта, вставьте следующее место в адресную строку и нажмите Enter. Затем выберите Корневой сертификат из этой папки и щелкните Открыто.
- В окне подтверждения убедитесь, что все поля доверия включены, прежде чем нажимать Хорошо.
- Перезагрузите браузер и проверьте, решена ли проблема.
Если вы все еще сталкиваетесь с sec_error_cert_signature_algorithm_disabled ошибка, перейдите к следующему способу ниже.
Метод 6: настройка значения security.pki.sha1_enforcement_level
Некоторые затронутые пользователи, у которых были проблемы с доступом к Facebook Workspace и нескольким другим аналогичным службам, сообщили, что проблема была решена после того, как они получили доступ к расширенным настройкам firefox и скорректировали Уровень обеспечения безопасности стоимость.
Эта процедура изменит конфигурацию вашего браузера Firefox для принятия Сертификаты SHA-1 без каких-либо дополнительных проверок, которые в конечном итоге устранят проблему. Однако, следуя этому маршруту, ваши сеансы просмотра могут остаться открытыми для атак безопасности.
Если вы решите пойти по этому пути, вам нужно сделать следующее:
- Откройте Firefox, введите ‘about: config‘На панели навигации и нажмите Enter, чтобы получить доступ к дополнительным настройкам.
- В запросе безопасности щелкните значок Я рискую! кнопка.
- Когда вы войдете в расширенные настройки Firefox, введите «security.pki.sha1»В поле поиска, чтобы найти значение, которое необходимо изменить.
- Затем дважды щелкните на security.pki.sha1_enforcement_level; 3 и измените значение на 4, прежде чем нажимать ОК.
- Перезагрузите браузер и посмотрите, решена ли проблема.
- Remove From My Forums
-
Вопрос
-
Hi. We have a Windows Server 2012 R2 Essentials server that is configured for Remote Web Access, and it has been working fine for a number of years. We are a home / small business customer, and just use a Microsoft-suppled
ourname.remotewebaccess.com domain name.Recently, we have begun receiving «site not secure» warnings from our browsers when attempting to connect to our server remotely. In Microsoft Edge, we receive the error:
The website’s security certificate has a weak signature and is not secure.
Error Code: DLG_FLAGS_WEAK_SIGNATURE
In Firefox, we see:
ourname.remotewebaccess.com uses an invalid security certificate. The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure. Error code:
SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLEDAny thoughts on how we should correct this? There is no certificate renewal process for Microsoft supplied domain names that I am aware of, and the RWA domain name wizard only provides options to procure a new domain name
or release the existing one, not an option to renew an existing one.I spent some time searching the forum but could not find a good match for our issue. Thank you in advance.
-
Изменено
11 августа 2017 г. 5:18
-
Изменено
Ответы
-
Hi,
I had found relate information about SHA-1 deprecation.
Microsoft security advisory: Deprecation of SHA-1 hashing algorithm for Microsoft root certificate program: January 12, 2016:
https://support.microsoft.com/en-us/help/3123479/microsoft-security-advisory-deprecation-of-sha-1-hashing-algorithm-forMicrosoft security advisory: SHA-1 deprecation for SSL/TLS certificates: May 9, 2017:
https://support.microsoft.com/en-us/help/4010323/titleMigrating your Certification Authority Hashing Algorithm from SHA1 to SHA2:
https://blogs.technet.microsoft.com/askds/2015/04/01/migrating-your-certification-authority-hashing-algorithm-from-sha1-to-sha2/In general, we can check the hashing algorithm of certificate:
Access the website using browser, right-click on the lock icon(if there is), click the option to view the certificate details, find option «Certificate Signature Algorithm» to confirm the certificate algorithm.If the certificate used for RWA is obtained automatically when enabling/configuring RWA, in order to re-obtain a new certificate for RWA on Windows Server Essentials, I would recommend you to dis-able RWA and re-enable it to confirm the result.
If the certificate is purchased/obtained manually, you may reference — Renew SSL Certificate for 2012 R2 Essentials:
http://kwsupport.com/2017/02/renew-ssl-certificate-for-2012-r2-essentials/Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Помечено в качестве ответа
Gary Voth
14 августа 2017 г. 22:24
-
Помечено в качестве ответа
Hi all!
I’ve inherited a bit of a mess at this job I started a while back. There’s a lot of unknowns in terms of what servers accomplish what tasks, where various things are, etc. This has very much been a detective role about as much as it’s been about computer tech.
Recently, several websites all of a sudden stopped working properly while using the office network. For example, we use Desktop Central, and I was looking into some information on ManageEngine’s site. This page DOES work Opens a new window Opens a new window, while this page does NOT Opens a new window Opens a new window (it’s linked from the first page). The first page uses a certificate from an organization named Sectigo Limited, and I get a closed padlock. The second page displays a certificate with an issuer name of «IssuingCA-ourLocalServer» and looking at the IssuingCA tab of the certificate, it has a bunch of stuff that references our company’s initials and such.
Firefox’s warning says:
.
Did Not Connect: Potential Security Issue
Firefox detected a potential security threat and did not continue to www.manageengine.com Opens a new window because this website requires a secure connection.
www.manageengine.com Opens a new window has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.
www.manageengine.com Opens a new window uses an invalid security certificate.
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
Error code: SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED
.
Today it was ManageEngine; yesterday it might have been some other (non-Spiceworks) forum I was trying to find an answer on; a few weeks ago, it was one specific page on the CDC site about COVID; before that it was the management site for Sophos AV. All of these had that same certificate in common, and I have no idea why «ourLocalServer» (not its name, but close enough) would be trying to sub in its own certificate in place of these other sites.
When I have trouble with sites during research, I can sometimes bypass the warning, or load a Google Cache version of the page. The CDC page started working by itself one day. For Sophos … that might contain a partial answer to my questions — we’d found that the site is hosted in Ireland, and our network admin had recently blocked all traffic in & out of the United States on the firewall, except for certain vendors.
Some sites / pages we visit will display an obvious message from the firewall saying «blocked because it’s located in {country outside the USA}.» Others aren’t so obvious, as I think the main site might be hosted in the states, while it uses resources that are overseas, so the site tries to reach those resources, but fails without being able to pass the message to the screen.
All that said, I’m really not sure what connection that ourLocalServer would have with the firewall, unless maybe the firewall is configured to pull certain things like certs from the server.
My questions are:
- Why would a company’s own server use its own certificate for remote websites?
- How do I find the certificate, and either fix it, remove it, or whatever needs done?
Hi,
I just had an amazin experience . I was trying to connect to a local webserver when Firefox gave me a sec_error_cert_signature_algorithm_disabled error. I was trying to ask our friend Google what this message exactly meant but was astonished when I got an exact result of 0 matches.
Now, I am here on Firefox 15, so maybe this is a newly introduced error code and hence there is no information out there yet.
Does anyone know how it can be «fixed» in the browser configuration (changing the webserver configuration is not an option)?
Posted April 30th, 2012, 8:26 am
Some info here on correcting cert errors and their causes >
http://support.mozilla.org/en-US/kb/Sec … &e=es&as=s
Your error is not specificly covered Good Luck
«The trouble with quotes on the internet is you never know if they are genuine» …Abraham Lincoln
Posted April 30th, 2012, 8:48 am
Also, since you are using a development build of Firefox it could also be a bleeding edge bug. If you register I can move this to our Builds Forum where the alpha is discussed.
Post wrangler
«Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default.»
Posted April 30th, 2012, 3:15 pm
I’m getting the same error when accessing pages over HTTPS on servers with self-signed certificates. The signature algorithm used on these certs is RSA-with-MD5. I’m in the process of trying again with using SHA256 to see if that fixes the issue. I’m also using Firefox Nightly builds.
Using yesterday’s version of Nightly, I got a different error (Error code: sec_error_bad_signature). It seems like this is a brand new error check (or bug) in today’s Nightly. That might explain why there are no Google results for the error (except for this forum page, apparently).
Posted April 30th, 2012, 3:44 pm
For what it’s worth, I’ve confirmed that if the certificate uses a stronger signature algorithm like SHA256, the error no longer appears (I just get the generic nag screen about using a self-signed cert).
Posted May 3rd, 2012, 7:34 am
Having the same issue here with self signed certificates. Seems to be an issue after the latest upgrade of the nightly 15.0a1
Return to Firefox Support
Who is online
Users browsing this forum: Bing [Bot] and 2 guests