kod.ldora.cn - Firefox blocks sites after remembering the mTLS certificate setup
Categories
(Core :: Security: PSM, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox117 | --- | affected |
People
(Reporter: rbucata, Unassigned)
References
()
Details
(Whiteboard: [psm-waiting])
From github: https://github.com/webcompat/web-bugs/issues/125856.
<!-- @browser: Firefox 117.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0 -->
<!-- @reported_with: desktop-reporter -->Browser / Version: Firefox 117.0
Operating System: Windows 11
Tested Another Browser: Yes EdgeProblem type: Something else
Description: The browser does not work properly after remembering the mTLS certificate setup
Steps to Reproduce:
When I open the website https://kod.ldora.cn, it will ask me for the certificate of authentication (mTLS has been enabled on the website). If I do not check the "Remember setting", I can access the website normally by manually selecting the certificate each time. But if I check the "remember Setting", the window for selecting the certificate will not pop up every time I visit the website. And all access is blocked because they are not mTLS certified
The test edge browser does not support the option to remember the domain name and certificate Settings, which need to be manually selected each time, and there is no problem
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/8/2b701d0a-ee2a-4b4a-a3d8-4be5ec2566da.jpeg">
</details><details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>buildID: 20230813180142</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>From webcompat.com with ❤️
Change performed by the Move to Bugzilla add-on.
Reporter | ||
Comment 1•2 years ago
|
||
The issue was reported via the webcompat.com reporter. Since it seems to be a browser issue as multiple pages (observed by the reporter) seem to exhibit this behavior, we have moved the issue. Please feel free to move the issue to the relevant project and component.
Reporter | ||
Updated•2 years ago
|
Thanks for the report. Can we ask the original reporter for some logs of the failing interaction?
Using about:logging
to file with the networking
preset may be sufficient and the logs can be emailed to necko@mozilla.com
Thanks!
Reporter | ||
Comment 3•2 years ago
|
||
I've made a comment on the issue with this request.
Comment 4•2 years ago
|
||
Not sure if the problem is just in the UI or deeper in the client certificate implementation.
Comment 5•2 years ago
|
||
The logs submitted by the user are saved at https://drive.google.com/file/d/14Z0ul8QdwQ4f3qIvtQ8pasFtrD3V33UQ/view?usp=sharing
![]() |
||
Comment 6•2 years ago
|
||
I commented in the github issue asking for further logs, but I haven't heard back yet.
Comment 7•1 years ago
|
||
![]() |
||
Comment 8•1 years ago
|
||
Thanks for the bump. I've asked for more information in the github report.
Description
•