https://bz.apache.org/ooo/show_bug.cgi?id=127418
Kyle H <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- Status|CLOSED |UNCONFIRMED --- Comment #2 from Kyle H <[email protected]> --- I object to this issue being closed as a duplicate of #125360. I am on Windows 10, not on MacOS. There is a group policy in place which prevents me from installing OpenOffice because of its lack of signature. I can install (and have installed) LibreOffice, but I'm told that OpenOffice is better than LibreOffice. It certainly has much more comprehensive SDK documentation available. More importantly, bug #125360 comment #3 suggests that there is a way to make this happen for Windows builds. Further, the blog post at https://blogs.apache.org/infra/entry/code_signing_service_now_available states "With projects like Apache OpenOffice, users expect to receive binaries that are ready to run. Today's desktop and mobile operating systems expect that binaries will be signed by the vendor -- which had left a gap to be filled for Apache projects." That blog post is now over 19 months old. OpenOffice has not moved forward with altering its build process to produce signed binaries or installers. Also, bug #125360 comment #4 suggests that OpenOffice has been "fully ready" to sign the Windows version for 18 months, since 11-17-2014. Why has this not happened yet? -- You are receiving this mail because: You are the assignee for the issue.
