Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.

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

  • 1 ответ
  • 1 имеет эту проблему
  • 7 просмотров
  • Последний ответ от 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.

Все ответы (1)

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

See: