This forum is a discussion about improving the "Unable to access secure (HTTPS) sites in Firefox 43" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

Link to Mozilla Security Blog post, change title ...and explain where to click "Advanced" to see the error

  • 6 Replies
  • Last reply by AliceWyman
  1. AliceWyman 5189 posts
    Report Abuse

    I approved the recent edit by philipp but the article still needs to be marked ready to localize.

    Also, the current title of this article is "I see SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED for HTTPS sites in Firefox".

    What about a better title, like HTTPS sites don't load in Firefox 43 ... or Unable to access secure (HTTPS) sites in Firefox 43?

    I also think this article could use a link to https://blog.mozilla.org/security/2016/01/06/man-in-the-middle-interfering-with-increased-security/ [*] for average users since the Microsoft and Google informational links are quite technical.

    [*] I made a new revision to reword the intro with a link to the Jan 6 2016 Mozilla Security Blog post.

    I approved the recent edit by philipp but the article still needs to be marked ready to localize. Also, the current title of this article is "I see SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED for HTTPS sites in Firefox". What about a better title, like '''HTTPS sites don't load in Firefox 43''' ... or '''Unable to access secure (HTTPS) sites in Firefox 43'''? I also think this article could use a link to https://blog.mozilla.org/security/2016/01/06/man-in-the-middle-interfering-with-increased-security/ [*] for average users since the [http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx Microsoft] and [https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/2-R4XziFc7A/YO0ZSrX_X4wJ Google] informational links are quite technical. [*] I made a new revision to reword the intro with a link to the Jan 6 2016 Mozilla Security Blog post.
    Modified by AliceWyman on
  2. AliceWyman 5189 posts
    Report Abuse

    Something else I noticed. The article says the following, under How do I know if this affects me?


    If you can access this article in Firefox, you're fine. Otherwise, try to access an HTTPS site like https://blog.mozilla.org, click “Advanced”, and if you see the error code “SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED”, then you’re affected.


    Where would you see the error code, exactly? In Firefox Options/Preferences > Advanced panel ?

    Something else I noticed. The article says the following, under '''How do I know if this affects me?''' ----- If you can access this article in Firefox, you're fine. Otherwise, try to access an HTTPS site like https://blog.mozilla.org, click “Advanced”, and if you see the error code “SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED”, then you’re affected. ----- Where would you see the error code, exactly? In Firefox Options/Preferences > [[Advanced panel - Accessibility, browsing, network, updates, and other advanced settings in Firefox|Advanced panel]] ?
  3. AliceWyman 5189 posts
    Report Abuse

    I approved the revision by Artist and marked the article ready to localize.

    We should still change the article title. My preference is: Unable to access secure (HTTPS) sites in Firefox 43

    I approved the revision by Artist and marked the article ready to localize. We should still change the article title. My preference is: '''Unable to access secure (HTTPS) sites in Firefox 43'''
  4. Tonnes 63 posts
    Report Abuse

    I did a small edit in order to avoid some possible confusion, which may answer the Advanced panel question above (see this screenshot provided by Philipp). I know this would create an inconsistency with the Blog text but the wording in the blog may not be leading nor perfect.

    I agree with changing the title since users may not note the error code at first instance - they should see "Your connection is not secure" if I understand correctly - and search for that, so searching the KB for the code while the article instructs users to click a button to find it doesn’t make sense.

    Note that there is this What do the security warning codes mean? article which isn’t linked. Thinking of it now, how about merging them? If not, the emphasis in the title of this article may need to be more on the "sudden" nature of this message appearing, probably not by including the SHA1 change, but more like "I can no longer access...", so Unable to access secure (HTTPS) sites in Firefox 43 as you suggested may quite well cover that.

    If adding this info into the What do the security warning codes mean? article) is an option or even in any case for that article, the difference in being able to add an exception or not caused by HSTS may need to be mentioned, including a screenshot. I’ve seen (non-Sumo) forum users struggling about why some users could and others could not do so after a website certificate expired and also wondered myself. Apparently users landing on an HSTS requiring website for the first time are able to add an exeption while regular visitors are not, caused by the browser’s behavior/caching IIUC (source: Philipp).

    There is also the Secure connection failed and Firefox did not connect article which may exist for a different cause, but it makes me wonder about the title(s) for any of these messages and their consistency. Not sure if linking to/from it would be needed.

    Another thing in this current article is: "If you can access this article in Firefox, you're fine. Otherwise, if you see the error when trying to access an HTTPS site like https://blog.mozilla.org". It may be a bit weird to give an example of an external https page while this article could/should suffer the same - even though you can’t say "if you can’t read this text, you are affected." :) In other words, there is an assumption of the user landing on this KB article using a different / unaffected browser, right?

    I did a small edit in order to avoid some possible confusion, which may answer the Advanced panel question above (see [https://camo.derpicdn.net/b6008c91048aec2196ad142e0640558a3826288a?url=http%3A%2F%2Fi.imgur.com%2FBQ554I6.png this screenshot provided by Philipp]). I know this would create an inconsistency with the Blog text but the wording in the blog may not be leading nor perfect. I agree with changing the title since users may not note the error code at first instance - they should see "Your connection is not secure" if I understand correctly - and search for that, so searching the KB for the code while the article instructs users to click a button to find it doesn’t make sense. Note that there is this [[What does "Your connection is not secure" mean?]] article which isn’t linked. Thinking of it now, how about merging them? If not, the emphasis in the title of this article may need to be more on the "sudden" nature of this message appearing, probably not by including the SHA1 change, but more like "I can no longer access...", so '''Unable to access secure (HTTPS) sites in Firefox 43''' as you suggested may quite well cover that. If adding this info into the [[What does "Your connection is not secure" mean?]] article) ''is'' an option or even in any case for that article, the difference in being able to add an exception or not caused by HSTS may need to be mentioned, including a screenshot. <sub> I’ve seen (non-Sumo) forum users struggling about why some users could and others could not do so after a website certificate expired and also wondered myself. Apparently users landing on an HSTS requiring website for the first time are able to add an exeption while regular visitors are not, caused by the browser’s behavior/caching IIUC (source: Philipp).</sub> There is also the [[Troubleshoot the "Secure Connection Failed" error message]] article which may exist for a different cause, but it makes me wonder about the title(s) for any of these messages and their consistency. Not sure if linking to/from it would be needed. Another thing in this current article is: "If you can access this article in Firefox, you're fine. Otherwise, if you see the error when trying to access an HTTPS site like https://blog.mozilla.org". It may be a bit weird to give an example of an external https page while this article could/should suffer the same - even though you can’t say "if you can’t read this text, you are affected." :) In other words, there is an assumption of the user landing on this KB article using a different / unaffected browser, right?
    Modified by Tonnes on
  5. AliceWyman 5189 posts
    Report Abuse

    Thanks. I changed the article title to Unable to access secure (HTTPS) sites in Firefox 43 and I also managed to add a "see also" link to What do the security warning codes mean? by adding it as a related articledocument in the Description. Both articles are now cross-linked.

    I don't know about merging the two articles like you suggested, since this article is more narrowly focused. I'll link to this discussion in that article, though.

    I also made a new revision based on yours to include https://support.mozilla.org as another example of an HTTPS website and self-approved as ready to localize.

    Thanks. I changed the article title to '''Unable to access secure (HTTPS) sites in Firefox 43''' and I also managed to add a "see also" link to [[What does "Your connection is not secure" mean?]] by adding it as a related <s>article</s><sub>document</sub> in the Description. Both articles are now cross-linked. I don't know about merging the two articles like you suggested, since this article is more narrowly focused. I'll link to this discussion in that article, though. I also made a new revision based on yours to include https://support.mozilla.org as another example of an HTTPS website and self-approved as ready to localize.
    Modified by AliceWyman on
  6. AliceWyman 5189 posts
    Report Abuse

    P.S. I noticed that "This Connection is Untrusted" error message appears - What to do is also a related document ("See also" link). I'm guessing philipp added it when he created this article?

    Why Secure connection failed and Firefox did not connect isn't included as a related document, I don't know. I created a new thread in that article's kb forum linking to this discussion.

    P.S. I noticed that [["This Connection is Untrusted" error message appears - What to do]] is also a related document ("See also" link). I'm guessing philipp added it when he created this article? Why [[Troubleshoot the "Secure Connection Failed" error message]] isn't included as a related document, I don't know. I created a new thread in that article's kb forum linking to this discussion.
    Modified by AliceWyman on
  7. AliceWyman 5189 posts
    Report Abuse

    AliceWyman said

    I also managed to add a "see also" link to What do the security warning codes mean? by adding it as a related articledocument in the Description. Both articles are now cross-linked.

    I removed that "see also" link because What do the security warning codes mean? was written for fx44, not fx43. I started a new discussion thread: https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean/discuss/6480 Update this article to apply to Firefox 43?

    ''AliceWyman [[#post-13086|said]]'' <blockquote> I also managed to add a "see also" link to [[What does "Your connection is not secure" mean?]] by adding it as a related <s>article</s><sub>document</sub> in the Description. Both articles are now cross-linked. </blockquote> I removed that "see also" link because [[What does "Your connection is not secure" mean?]] was written for fx44, not fx43. I started a new discussion thread: https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean/discuss/6480 ''Update this article to apply to Firefox 43?''
    Modified by AliceWyman on