https://bugs.documentfoundation.org/show_bug.cgi?id=133941
Moritz Duge (a.k.a. kolAflash) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #9 from Moritz Duge (a.k.a. kolAflash) <[email protected]> --- @Timur So it seems there was a misunderstanding about the functionality of the existing "Certificate Manager" button at the beginning of this ticket. I changed to UI in August 2024, so it reflects that the existing button is only for GPG (OpenPGP). See comment #6 -> So would it be OK to close the ticket now? Or should the ticket stay open to get a second button for the X.509 certificate management? I guess having an extra X.509 management button would implicate some work. Because on Windows certmgr.msc is being used, while all other platforms use profiles from Mozilla software for X.509. And it's even not obvious which Mozilla binary to start for that. Thunderbird, Firefox or SeaMonkey and you may have multiple installations of each at random places. In theory it would be nice to have a single certificate management for all. But in practice I see no easy solution for that. Windows and macOS inbuild certificate managers (certmgr.msc and macOS Keychain) only support X.509 as far as I know. Kleopatra+GPG would in theory be an alternative, but users need to install it first and I guess Windows X.509 users strongly prefer certmgr.msc. -- You are receiving this mail because: You are the assignee for the bug.
