We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

sec_error_unknown_issuer on sites without intermediate certs

  • 3 antwoorden
  • 1 heeft dit probleem
  • 2 weergaven
  • Laatste antwoord van 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?

Alle antwoorden (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