Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

After update to 38.0.5 Firefox thinks a certificate with wildcard is invalid but it's not

  • 1 wotmołwa
  • 1 ma tutón problem
  • 7 napohladow
  • Poslednja wotmołwa wot cor-el

tmcgreevy
tmcgreevy
more options

We have an internal CA server that we've used for a long time for signing internal SSL certs. One B2B appliance with two NICs - one for for management and one for normal traffic. We have one certificate with a wildcard to cover both DNS names/addresses.

Before updating Firefox to 38.0.5, this worked with no problem. Now Firefox reports the cert is invalid. IE has no problem with the certificate either.

We have an internal CA server that we've used for a long time for signing internal SSL certs. One B2B appliance with two NICs - one for for management and one for normal traffic. We have one certificate with a wildcard to cover both DNS names/addresses. Before updating Firefox to 38.0.5, this worked with no problem. Now Firefox reports the cert is invalid. IE has no problem with the certificate either.

Wšě wotmołwy (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See: