With Okular now used for signing Qualified signatures become more important.
Kleopatra should show this in the certificate details. For testing you might use the "qualified.txt" (although werner is not sure if this still works)
With Okular now used for signing Qualified signatures become more important.
Kleopatra should show this in the certificate details. For testing you might use the "qualified.txt" (although werner is not sure if this still works)
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA0e7b8ad3aa8b CertificateDetailsWidget: Show qualified status for SMIME certificates | |||
| rKLEOPATRAd72c8e02e1ca CertificateDetailsWidget: Show qualified status for SMIME certificates | |||
| rKLEOPATRAe2e6167f732b CertificateDetailsWidget: Show qualified status for SMIME certificates | |||
| rKLEOPATRAce39e0f0d0f9 CertificateDetailsWidget: Show qualified status for SMIME certificates | |||
Werner mentioned that the keyword "qual" can also be used like the "relax" keyword can also be used in the global trustlist.txt
(writing this much later, since got lost)
Since this never specified exactly how it should look, here's what's been implemented:
Gpg4win-5.0.0-beta476:
I've created a global trustlist.txt at C:\ProgramData\GNU\etc\gnupg with an entry for the RootCA for Werners QES key with the qual keyword. (The local config would not work, according to the man page.)
But after restarting Kleopatra and it's background processes I do not see "qualified signature" for Werners key:
If I did something wrong, please point me in the right direction
What does gpgsm -k --with-colons print for Werner's QES key? The usage / capabilities should contain s (for signing) and q (for qualified signing). If q is missing then something isn't set up correctly.