https://bugs.documentfoundation.org/show_bug.cgi?id=139449
--- Comment #3 from [email protected] --- Hi, I got this bug when trying to sign LibreOffice files (.odt .ods .odg .odp ) with an x509 cert (sorry I didn't mention it in the first report, I even think OpenPGP wasn't a thing back then). However, an update: I've updated all the software: * LOO 7.6.2.1 * Gemalto SafeNet Authentication Client 10.8 R9 (10.8.2725.8) - token's drivers - * Still Windows 10 Enterprise LTSC x86_64 tho And the situation is the same: The signature IS available and listed in File > Digital Signatures > Sign Document, but when selected (double click on certificate line) nothing will happen, and will be returned to the File > Digital Signatures screen with no signature applied at all. The certificate and private key also appears in windows cert store, and can be used by other applications. * Tested this time with Thunderbird 115.4.2 The problem just seems to be when trying to sign LOO files, since I can sign PDF files just fine using the File > Export As > Export As PDF... > Digital Signatures. ABOUT SIGNING WITH OPENPGP SIGNATURES: Just tested it (Gpg4win 4.2.0), and I can sign LOO files without any problems (wonderful!) So, the problem seems to occur ONLY when trying LOO files (PDF are ok) with an x509 key/cert. Token appears to function ok since it can be used by every other program to sign/verify, and even LibreOffice seems to be capable to access it considering Draw can use the stored certs to sign existing PDFs correctly (I can do this even without having gpg4win installed, so I would say it doesn't rely on it at all -speaking of x509 signatures-). -- You are receiving this mail because: You are the assignee for the bug.
