Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Trang web này sẽ có chức năng hạn chế trong khi chúng tôi trải qua bảo trì để cải thiện trải nghiệm của bạn. Nếu một bài viết không giải quyết được vấn đề của bạn và bạn muốn đặt câu hỏi, chúng tôi có cộng đồng hỗ trợ của chúng tôi đang chờ để giúp bạn tại @FirefoxSupport trên Twitter và /r/firefox trên Reddit.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

SEC_ERROR_BAD_SIGNATURE returned on private PKI containing intermediate CA

  • 2 trả lời
  • 1 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi cosmin.banu

more options

I am trying to browse websites through a proxy that intercepts the TLS connections and signs the certificates using a private CA certificate.

If I'm using only a root CA certificate, setting it on my proxy as well as in the OS's certificates store, I can browse the internet without any issues. The chains in this case would be: Root CA -> Server Certificates

However, my setup mandates that I use an intermediate CA on the proxy. The chains in this case would be: Root CA -> Intermediate CA -> Server Certificates If I add an intermediate CA to the proxy and the root CA to my OS's certificates store, I get the following error:

" Secure Connection Failed An error occurred during a connection to www.youtube.com. Peer’s certificate has an invalid signature. Error code: SEC_ERROR_BAD_SIGNATURE

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

"

I'm using Firefox 82.0.2 on Windows 10.

How can I get more details on why it's failing? I've tried looking in the "Security" tools tab, but I see only this error ID.

Thank you, Cosmin

I am trying to browse websites through a proxy that intercepts the TLS connections and signs the certificates using a private CA certificate. If I'm using only a root CA certificate, setting it on my proxy as well as in the OS's certificates store, I can browse the internet without any issues. The chains in this case would be: Root CA -> Server Certificates However, my setup mandates that I use an intermediate CA on the proxy. The chains in this case would be: Root CA -> Intermediate CA -> Server Certificates If I add an intermediate CA to the proxy and the root CA to my OS's certificates store, I get the following error: " Secure Connection Failed An error occurred during a connection to www.youtube.com. Peer’s certificate has an invalid signature. Error code: SEC_ERROR_BAD_SIGNATURE The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. " I'm using Firefox 82.0.2 on Windows 10. How can I get more details on why it's failing? I've tried looking in the "Security" tools tab, but I see only this error ID. Thank you, Cosmin

Giải pháp được chọn

I've found the root cause. The chain was incorrectly constructed, there was a mismatch between the server certificate's issuer field and the subject of the CA certificate.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (2)

more options

Update:

I've reproduced this on two setups now on Windows 10, in different PKI configurations (both using an intermediate CA), using: - Firefox 82 - Firefox nightly 65 - Firefox nightly 84

On Linux (Debian 10) it works, using: - Firefox ESR 78.4

I've tested some other browsers on Windows 10, as well, they all work fine: - Chrome - Opera - Vivaldi - Edge

Is there a way to get some detailed debug logs on Firefox on Windows 10?

Thank you, Cosmin

more options

Giải pháp được chọn

I've found the root cause. The chain was incorrectly constructed, there was a mismatch between the server certificate's issuer field and the subject of the CA certificate.