Bug 133941 - Start Certificate Manager in Windows should start certificates system store
Summary: Start Certificate Manager in Windows should start certificates system store
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: framework (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: Digital-Signatures
  Show dependency treegraph
 
Reported: 2020-06-12 19:17 UTC by Timur
Modified: 2021-09-16 08:01 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2020-06-12 19:17:54 UTC
In Windows 7 LO uses Windows certificates system store (which makes sense) to sign ODF and PDF.
But with Start Certificate Manager it starts Kleopatra (which then doesn't make sense).
Start Certificate Manager should start Certificates (Certmgr.msc), a Microsoft Management Console (MMC) snap-in.
Comment 1 Buovjaga 2020-10-19 15:44:21 UTC
On Win 10 it says "Could not find any certificate manager."
File - Digital Signatures - Digital Signatures - Start certificate manager

Version: 7.1.0.0.alpha0+ (x64)
Build ID: df74aef7159d7155addf78cfc4d139485945d794
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: default; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded
Comment 2 Dario Andres Susman 2020-11-25 18:33:18 UTC
Hi!
I'm running a Windows 7 x64 which has the gpg4win package installed on another drive and LibreOffice 7.0.3.1 is unable to pick it up for PGP keys. 
May be a whole "Path to gpg4win directory" UI interface would be useful.

On a Windows 10 box, same LibreOffice version, and gpg4win installed on C: has no trouble finding the PGP keys.

Cheers,
Dario Susman
Comment 3 Olivier Hallot 2021-09-15 19:10:50 UTC
The defined apps for certificate management seems to be fixed in the code

https://opengrok.libreoffice.org/xref/core/xmlsecurity/source/dialogs/digitalsignaturesdialog.cxx?r=9940f077#456

And certmgr.msc is not listed there.

So I guess user *must* install one of the hard-coded tools to sign in windows 10.

Also, not sure certmgr.msc can handle GPG, which may be the reason for forcing gpg4win

-> doc.

(still LibreOffice cannot find X509 certs (Cacert) in the list of available certs)
Comment 4 Timur 2021-09-16 08:01:58 UTC
Thanks for comment. 
Seems that this should be changed so that there's option where from both certificates are used and certificates store started.