Comment 55 for bug 1771880
Revision history for this message
| Mark - Syminet (mark-syminet) wrote | #55 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi, thought I'd chime in here as just ran into the same issue on debian bullseye. Obtained an oh-so-precious "mycert.p12" file and resolved thus:
Step 1:
a) In Firefox ESR: Settings -> Privacy and Security -> View Certificates button (way down at the bottom).
b) "Certificate manager" popup window, "Your Certificates", Import button
c) Select mycert.p12 file and it appears in Firefox.
Step 2:
a) In LibreOffice Write: Tools -> Options -> Security, click "Certificate" button under "Certificate Path"
This is where it got interesting - there were two selections there:
x firefox:default
o firefox:default-esr
the top one, "firefox-default" was selected and was not working. Clicking "firefox:
Another important note: After changing the certificate path, it prompts "LibreOffice Write needs to restart in order to take effect. Do this now?" ...which I answered yes, but it did not actually restart. Initially thinking it didn't work. But upon manual restart, it *did* work.
Maybe this approach is better since it takes Seahorse out of the loop.
Would also be curious to know if Jammy is fixed and/or above works? I'm going to upgrade one of the three debian bullseye systems I did this on successfully, to debian bookworm right now. If anything breaks, I'll be sure to post that here.
Hope this helps someone out there.