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

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

Подробнее

"This Connection is Untrusted" page has no "I understand the risks" block.

  • 4 ответа
  • 14 имеют эту проблему
  • 6 просмотров
  • Последний ответ от unisay

more options

Security exception added manually in the "Certificate Manager" doesn't work. Self-signed certificate is issued for all subdomains: *.top.domain

Security exception added manually in the "Certificate Manager" doesn't work. Self-signed certificate is issued for all subdomains: *.top.domain

Изменено unisay

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

more options

Separate Issue: Update your Flash Player (Linux) Version 11.2.202.481
https://www.adobe.com/products/flashplayer/distribution3.html

See if there are updates for your graphics drivers https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration


I've called the big guys to help you. Good luck.

more options

If you can't inspect the certificate via "I Understand the Risks" then try this:

Open this chrome URI by pasting or typing this URI in the location/address bar to open the "Add Security Exception" window and check the certificate:

  • chrome://pippki/content/exceptionDialog.xul

In the location field type/paste the URL of the website

  • retrieve the certificate via the "Get certificate" button
  • click the "View..." button to inspect the certificate in the Certificate Viewer
more options

I did this exception dialog before via: 1. Preferences > Advanced > Certificates > View Certificates > Servers > Add Exception. 2. Using developer tools remove attribute hidden="true" from the div in the "Untrusted Connection" page then click "Add exception"

So, in the Certificates Manager I can see that my certificate is added. Unfortunately, adding exception doesn't help in case of domain with *. (see *.cd.xxx.xx in the screenshot) However, I does help in case of explicitly specified subdomain (see stash.xxx.xx in the screenshot.)

cor-el said

If you can't inspect the certificate via "I Understand the Risks" then try this: Open this chrome URI by pasting or typing this URI in the location/address bar to open the "Add Security Exception" window and check the certificate:
  • chrome://pippki/content/exceptionDialog.xul
In the location field type/paste the URL of the website
  • retrieve the certificate via the "Get certificate" button
  • click the "View..." button to inspect the certificate in the Certificate Viewer
more options

Any update on this? Should I file a bugreport?