New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 9 users

Issue metadata

Status: WontFix
Closed: Dec 2011
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

  • Only users with EditIssue permission may comment.

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

Issue 107845: Receiving error "Security certificate is signed using a weak signature algorithm" when using a corporate proxy

Reported by, Dec 16 2011

Issue description

Since build 5639 of chromium, I get SSL errors for any sites attempting to use SSL encryption.

If I revert back to 5638 & clear out %userprofile%\Local Settings\Application Data\Chromium\User Data, it all works fine again.

Guessing it was this change,

When encountering certificates signed with md2/md4, make it a fatal error. When encountering certificates signed with md5, interstitial the page with an error about md5 being a weak signing algorithm. This excludes checking the signatures of root certificates (trust anchors), as their self-signed signatures are not relevant to the security of the chain. BUG= 101123  Review URL:

While the security improvement makes sense, is there any option to disable the check or is it just up to sites to update their cert signing?
80.4 KB View Download
80.3 KB View Download

Comment 1 by, Dec 16 2011

EDIT: Should have said certificate errors instead of SSL errors in description & attachments.

Comment 2 by, Dec 16 2011

Labels: -Area-Undefined Area-Internals Internals-Network-SSL

Comment 3 by, Dec 16 2011

Is there something special about your setup, i.e. a MITM proxy?

The patch certainly wasn't intended to break major sites and it doesn't cause problems for either nor for me.

If you click the padlock on the certificate error page, who does it say is signing the certificates for those sites?

Comment 4 by, Dec 16 2011

Certs are by Microdasys Root CA so it may me a proxy issue.
26.1 KB View Download
25.8 KB View Download

Comment 5 by, Dec 16 2011

Status: Assigned
Ok, I'll try and contact Microdasys - thanks for the report. (I assume that you're on a corporate machine as private root CAs shouldn't work unless they have been specifically configured.)

In the mean time, the dev channel should work to get you back online.

Comment 6 by, Dec 16 2011


Comment 7 by, Dec 16 2011

agl: This does seem me, not palmer. Palmer's change would be ERR_CERT_WEAK_KEY, but this corresponds to ERR_CERT_WEAK_SIGNATURE_ALGORITHM.

Depending on how frequently we think this to appear, we could adopt a similar posture as some of the pinning errors - only make weak sig algs troublesome for certs chaining to an "OS root". But I'd like to avoid that, if possible, as the interstitial/error serves an evangelism purpose as much as a security purpose.

Comment 8 by, Dec 16 2011

Yes, we should try to contact Microdasys first.  We have a lot of time
before Chrome 18 arrives on the Beta chanel.

Comment 9 by, Dec 17 2011

Summary: Receiving error "Security certificate is signed using a weak signature algorithm" when using a corporate proxy

Comment 10 by, Dec 20 2011

I've received no reply from the email that I sent to Microdasys and all their listed phone number have been disconnected. I think it's a dead company so it's unlikely that we're going to get them to update anything.

Comment 11 by, Dec 20 2011

Do we all agree that this error is true, that we should not special-case private root CAs for the weak key problem, and that since Microdasys appears to be dead, the bug reporter's company should get a new MITM proxy or try to set a new root cert that uses a modern signing algorithm?

If we do all agree, we should mark this bug WontFix (working as intended).

Comment 12 by, Dec 20 2011

Status: WontFix
palmer: I think that's probably the case, although I don't feel great about it. None the less I'd like to watch to see how big an impact it will have.

But, for now, I agree that it's probably a WontFix.

Comment 13 by, Dec 20 2011

Labels: Mstone-18
palmer: marking this WontFix is fine by me.

Re: your comment 11: getting a new root CA cert won't help.  It is
the signature algorithm used by the root CA that matters.

blaquewraith: can you find out if the Microdasys proxy can be configured
to sign certificates using SHA-1 instead of MD5?

Comment 14 by, Dec 21 2011

Microdasys actually got back to me (it seems that they aren't completely dead after all) and reported that they'll be updating their product to sign with SHA-1.

Comment 15 by, Jan 3 2012

Apologies for delay in replying, I was away over the holidays.

Thanks for investigation, will stick with build 5638 until we get an update for the proxy.

Comment 16 by Deleted ...@, Apr 21 2012

RSA-MD2 is not weak when the key length is long enough.  This is a bogus message, debate on whether to use DSA vs RSA is mute.  Please remove this warning, it is next to useless unless the RSA key is too short and there is little chance of that these days.

Comment 17 by Deleted ...@, Jun 12 2012

My name is Claudette Moran, and this same exact problem occured on my Google Chrome as well!:( I am NOT able to log into my gmail, hotmail,or Facebook accounts in anyway, shape or form!:( Since my sister is the one that is paying of the internet service of Clearwire from her laptop, she claims tghat there is NOTHING WRONG with the PC my mother and I use, which is separate from her laptop. I have limited time to check the SSL certificate, much less remove and put back Google Chrome as a separate icon to use. Every time that I clicked on the red padlock, it states that the SSL certificate is fine. It states that it's an scha5. What do I need to do to change this, as I am NOT a computer programer. My younger brother is, but he has no time whatsoever to change the SSL/HTTPS certificate.PLEASE HELP!

Comment 18 by, Jun 12 2012

claudettemoran: it sounds unlikely that you're using a corporate proxy at home.

This is more likely to be the fault of firewall/anti-virus software that's trying to intercept HTTPS traffic. If you go to and click the padlock, the top of the dialog should say "The identity of this website has been verified by ...". The name that follows might give a hint about which software is causing the problem.

Otherwise, try configuring any anti-virus or firewall software not to scan within HTTPS connections.

Comment 19 by Deleted ...@, Jun 12 2012

Thank you. I will try that. No, I am at the library, so  I was able to log on to my gmail account there. Thanks.

Comment 20 by, Oct 13 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 21 by, Mar 10 2013

Project Member
Labels: -Area-Internals -Internals-Network-SSL -Mstone-18 Cr-Internals-Network-SSL M-18 Cr-Internals

Comment 22 by, Mar 13 2013

Project Member
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Sign in to add a comment