<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - OpenPGP / GnuPG issues"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=118478">118478</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>OpenPGP / GnuPG issues
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>6.0.5.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>brian@brianzech.com
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="http://bugs.documentfoundation.org/attachment.cgi?id=143245" name="attach_143245" title="Digital Signatures window">attachment 143245</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=143245&action=edit" title="Digital Signatures window">[details]</a></span>
Digital Signatures window
Ubuntu 18.04 MATE
LibreOffice Version: 6.0.5.2
Build ID: 1:6.0.5~rc2-0ubuntu0.18.04.1~lo1
CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); Calc: group
OpenPGP does not appear to be working at all. This report appears to be a semi
duplication of other reports, but they are only similar and not mentioning
Linux, but MacOS and Windows.
1) Go to Tools -> Options -> User Data, under Cryptography there is OpenPGP
Signing Key and OpenPGP Encryption Key. Both show "No Key" and the pull down
lists nothing more to select, ie. none of my keys appear.
2) Go to File -> Digital Signatures -> Digital Signatures, I an given a window,
blank in content, with the options of "Sign Document" and "Start Certificate
Manager" [see attached screenshot]. I click to start certificate manager, and
from there Seahorse opens and I can see and verify all of the keys and
certificates I expect to see and have available to me. So, I click to sign
document. I am then asked to select a certificate, and only X.509 options are
there.
Unless I am missing something, those are the only places I find to use PGP keys
to sign a document. I currently have numerous X.509 certs and PGP keysets on my
system, all working properly. I have enigmail, gnupg, seahorse, gpg, and other
key management and dev tools installed. I am able to generate and manage keys
without issues, and use keys PGP and SSH keys without issue for basic messages,
email, remote connectivity, etc. This issue is not new for me to this version,
it has been existing for a while. I am reporting now as the need to use came up
again and it is still not functional.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>