Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Since a week ago, get SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED appear when connecting to site with Geotrust certificate, which has been working for two years

  • 2 replies
  • 4 have this problem
  • 1 view
  • Last reply by JLaerkedal

JLaerkedal
JLaerkedal

Lync site "meet.dkpto.dk". Certificate test at Geotrust check shows no error. Certificate has been working for a couple of years, stand to expire January 2018. No reasonale explanation given by Firefox. Server frontend does not allow other ciphers than TLS 2.1.

Lync site "meet.dkpto.dk". Certificate test at Geotrust check shows no error. Certificate has been working for a couple of years, stand to expire January 2018. No reasonale explanation given by Firefox. Server frontend does not allow other ciphers than TLS 2.1.

Chosen solution

Have now replaced the certificate with one of same type, but using a more recent intermediate. This has made the error go away, but I do not know, if the problem came from the original intermediate using SHA-1, or if there was a problem with the original root certificate. Might as well close the case, as the problem can no longer be reproduced by now. Best regards Jens Lærkedal.

Read this answer in context 👍 0

All Replies (2)

JLaerkedal
JLaerkedal Question owner

Geotrust indicates, that the problem possibly comes from the intermediate certificate being signed with SHA-1. Could this be the "problem", even though the server is set up to not allow unsecure ciphers? Best regards Jens Lærkedal

JLaerkedal
JLaerkedal Question owner

Chosen Solution

Have now replaced the certificate with one of same type, but using a more recent intermediate. This has made the error go away, but I do not know, if the problem came from the original intermediate using SHA-1, or if there was a problem with the original root certificate. Might as well close the case, as the problem can no longer be reproduced by now. Best regards Jens Lærkedal.