Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 1 antwurd
  • 1 hat dit probleem
  • 7 werjeftes
  • Lêste antwurd fan 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.

Alle antwurden (1)

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

See: