https://bugs.freedesktop.org/show_bug.cgi?id=86780
Christian Lohmaier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW URL| |http://msdn.microsoft.com/e | |n-us/library/windows/deskto | |p/aa378132(v=vs.85).aspx CC| |[email protected] | |rg Ever confirmed|0 |1 --- Comment #2 from Christian Lohmaier <[email protected]> --- this is more or less a wontfix. Of course we cannot fix the already released builds, and not sure whether TDF will switch certificates... (nothing needs to be changed in the code though) The problem is not wrong way of signing, but as it turns out the certificate (we use Class 2 code-signing certificate from StartCom) actually has a flag that limits the validity of the signature to that of the certificate (doh!) I didn't know of that flag, so I (and I guess everyone else) assumed that timestamping the builds will take care of things.. Our certificate has the 1.3.6.1.4.1.311.10.3.13 - Microsoft's OID "szOID_KP_LIFETIME_SIGNING" defined. We'd need an "Extended Validation" type that doesn't have that restriction (but of course also costs more)... Anyway, confirmed. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
