Am running mac osx 10.13.3 with LO 18.104.22.168.alpha0+ Master and GPG Suite 2018.1 (gpgtools.org).
I have an issue with Digital Signatures. After raising the issue on https://bugs.documentfoundation.org/show_bug.cgi?id=89037#c9 I was advised to try and test on Master and the situation remains the same.
Basically no Digital signatures are listed in File/Digital Signatures/Digital Signatures even though I have a valid OpenPGP key (Usable in Mail.app).
Clicking on Start Certificate manager, I get an error "Could not find any certificate manager".
Documentation is scanty on the process involved in Mac OS but from reviewing what the official documetation describes (Windows) it seems LO is unable to pick keys/certificates from the GPG Suite or even recognize the suite as a valid certificate manager.
Am willing to try out any leads, pointers that may be availed.
Steps to Reproduce:
1. Save document on Mac OS LO
2. Go to File/Digital Signatures/Digital Signatures.
3. Click on Start Certificate Manager.
Nothing is listed on the Digital Signatures.
An error is displayed on clicking Start Certficate Manager. "Could not find any certificate manager"
List the keys in GPG Keychain and be able to appy them to the current document.
User Profile Reset: No
Build ID: a488c7ad2763b944713997911c1ddb0315d8c93f
CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default;
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-26_00:38:29
Locale: en-GB (en_GB.UTF-8); Calc: group
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Hmm, so I had it working with a comparable setup end of last year (slightly older OSX, and GPGTools versions). I presume GPG keys work just fine in emails?
(In reply to Thorsten Behrens (CIB) from comment #1)
> Hmm, so I had it working with a comparable setup end of last year (slightly
> older OSX, and GPGTools versions). I presume GPG keys work just fine in
Just sent @THB a signed reply from Mail App to show GPG keys working. Didnt know how to CC the other users directly from the email client.
*** This bug has been marked as a duplicate of bug 115538 ***