Having extensive PKI experience I tried digital signature signing with Writer (V3.4.2 release). I am not sure this feature is "writer" specific - but suspect that writer would be the most use LibO app for signature. Overall the feature seems pretty close but needs to tweaks to be "end user" ready. Specifically the following things need to be fixed: 1) certificates that have expired must not be “offered/available” for selection for signature. 2) Certificates that do NOT have the "key usage = verification" must not be offered for signature. Only certificates that have the proper key usage for signature should be elible for signature. In my test case – I have “encryption” only certificate(s) – which were displayed when the “sign document” button is selected. I have signed the attached document with my EFS certificate – which has a “Key Usage=Encipherment” - which MUST NOT be possible. 3) Certificate purpose display does not display any values. I have attached screen grabs from LibO and MS CAPI to show comparison. Why not just use the MS interface to "view certificates" (at least on windows). 4) all certificates in Microsoft CAPI are enumerated – but an access to the private key is made before the certificate is selected to be signed. The only certificates that are displayed are those that a private key access is successful. What should happen is that all certificates in CAPI (subject to the above “filtering” improvements”) are displayed – but accessing the private key should only happen once the end user selects the particular certificate to sign with. This is big problem for any certificate that is protected in key store not yet open/access (like smartcards). 5) The “view certificate/details” tab should display – Key Usage, Extended Key Usage and SubjectAltName. Over all I suggest that certificate display should use Microsoft interface on Windows. Thanks...
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Thanks for bugreport Please, verify if in last version of LibreOffice still reproducible
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian