Bug 156891 - "Start Certificate Manager" button is disabled while gpg4win is actually installed
Summary: "Start Certificate Manager" button is disabled while gpg4win is actually inst...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Digital-Signatures
  Show dependency treegraph
 
Reported: 2023-08-24 11:03 UTC by Hossein
Modified: 2023-08-29 10:13 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hossein 2023-08-24 11:03:06 UTC
Description:
While trying to open certificate manager, "Start Certificate Manager" is disabled. I have installed Gpg4win, and I have Kleopatra installed and running.

Steps to Reproduce:
1. Install latest gpg4win from here:
https://files.gpg4win.org/gpg4win-4.2.0.exe
2. Open a file LibreOffice.
3. Open "File > Digital Signatures > Digital Signatures"
4. Try using "Start Certificate Manager".

Actual Results:
The "Start Certificate Manager" button is disabled.

Expected Results:
It should not be disabled, and it should open "Kleopatra".


Reproducible: Always


User Profile Reset: No

Additional Info:
Reproducible in:
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bfa81a200ab59971b69823f9a29d8ce222d655e6
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: CL threaded

Not reproducible in:
Version: 7.6.0.3 (X86_64) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_DE); UI: en-GB
Calc: CL threaded
Comment 1 Mike Kaganski 2023-08-24 11:11:28 UTC
Isn't the certificate manager here completely unrelated to GPG? I believe, that it's about system certificates, not GPG.
Comment 2 Mike Kaganski 2023-08-24 11:15:17 UTC
The respective help [1] (push the button in the dialog) tells:

> Start Certificate Manager
> Opens the installed certificate manager of your system.
> 
> On Windows systems, the default certificate manager is Certmgr.msc, a Microsoft
> Management Console snap-in using Certmgr.exe, and does not manage OpenPGP
> certificates. To manage both X509 and OpenPGP certificates install the gpg4win
> tool.

I believe that it tells that this button is not going to use gpg4win, but it's an awkward way of telling "use external app to manage them". Disclaimer: I did not read the code.

[1] https://help.libreoffice.org/24.2/en-US/text/shared/01/digitalsignatures.html?System=WIN&DbPAR=WRITER&HID=xmlsec/ui/digitalsignaturesdialog/dialog-action_area1#bm_@@nowidget@@
Comment 3 Hossein 2023-08-24 12:45:38 UTC
(In reply to Mike Kaganski from comment #1)
> Isn't the certificate manager here completely unrelated to GPG? I believe,
> that it's about system certificates, not GPG.
I think it should open Kleopatra. You can try the 7.6 and see it working, opening Kleopatra. In master, "Tools > Options > LibreOffice >  Security" has extra section, "Certificate Manager" that shows custom certificate executable. For me, it is: "C:\Program Files (x86)\Gpg4win\bin\kleopatra.exe", which is the valid path to the executable.

This is part of the nice GSoC work by "Ahmed Eltokhy". Please see hispatch:
https://gerrit.libreoffice.org/c/core/+/153798

I had a discussion with Ahmed, and he will check this Windows-specific issue, possibly arising from how the above path is used for running the certificate manager on Windows.

I am adding him to CC.
Comment 4 Heiko Tietze 2023-08-29 07:00:50 UTC
(In reply to Mike Kaganski from comment #1)
> Isn't the certificate manager here completely unrelated to GPG? I believe,
> that it's about system certificates, not GPG.

Tokhy put some effort during the GSoC project into this with https://gerrit.libreoffice.org/c/core/+/153798. And apparently there are a few bits unresolved.

Confirmed the issue during a call => NEW