In the reporting on whether or not the digital signatures on a document have a problem, assigning the most severe problem level to all signatures on the document prevents accurate trouble-shooting. RECOMMENDATION 1. It is fine to assign the most severe level to the document and in the indicator for the document. This will result in it being either all signatures valid, some certificates could not be validated (or there are other issues, such as not all parts signed, unable to check for Certificate Revocation or a certificate is revoked/out-of-date) or some signatures are invalid. 2. However, when the individual signatures are listed, they should not all be identified with the same severity. That makes it difficult to trouble-shoot the situation and attempt to track down the root cause by users and administrators. The signatures should be identified individually with respect to verification of signatures and the validation of the certificate. 3. Finally, although this is a bigger feature issue, it does not appear that LibO will check for Certificate Revocation or indicate that it is unable to do so (e.g., no on-line connectivity, the CRL site is not responding). 4. From the Help Pack digital signatures overview subtopic, it is not possible to determine what the behavior is if a Certificate has expired and whether it appears to have been signed before expiration/revocation or not. This should be clarified in the implementation and the Help Pack and on-line Help.
[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
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
*** This bug has been marked as a duplicate of bug 36970 ***