当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

sec_error_unknown_issuer on sites without intermediate certs

  • 3 件の返信
  • 1 人がこの問題に困っています
  • 2 回表示
  • 最後の返信者: philipp

more options

Why in this day and age is this still an issue with Firefox alone. Sites that do not have the intermediate cert installed, cause an error in Firefox (sec_error_unknown_issuer). I understand the technical reason why this happens, but my question is why doesn't the Firefox foundation do something about it? The sites are not inherently insecure and to the user you are making it look like it is.

All of the sites correctly work in every other modern day browser: IE11, Safari 8, Chrome (43) except Firefox. Why would all of those other browser make the decision to allow it, but not Firefox?

Why in this day and age is this still an issue with Firefox alone. Sites that do not have the intermediate cert installed, cause an error in Firefox (sec_error_unknown_issuer). I understand the technical reason why this happens, but my question is why doesn't the Firefox foundation do something about it? The sites are not inherently insecure and to the user you are making it look like it is. All of the sites correctly work in every other modern day browser: IE11, Safari 8, Chrome (43) except Firefox. Why would all of those other browser make the decision to allow it, but not Firefox?

すべての返信 (3)

more options

hello, it is necessary to have a full link from a server certificate to the certificate authorities in the browser's root trust store - otherwise the whole cert system won't work. what solutions would you propose?

more options

Why cannot it be solved in the same manner as: IE11, Safari 8, Chrome (43) ?

more options

the reason why mozilla isn't going this approach is explained in https://bugzilla.mozilla.org/show_bug.cgi?id=399324