Apache OpenOffice and CVE-2016-1513
Apache OpenOffice and CVE-2016-1513
Posted Jul 28, 2016 1:41 UTC (Thu) by jmspeex (subscriber, #51639)Parent article: Apache OpenOffice and CVE-2016-1513
Posted Jul 28, 2016 15:15 UTC (Thu)
by branden (guest, #7029)
[Link] (1 responses)
Posted Jul 29, 2016 19:36 UTC (Fri)
by xtifr (guest, #143)
[Link]
At the current level of activity where they can't even manage to get a security fix out in a timely manner? Yes, it doesn't take many resources to maintain a project really poorly. :)
The question is, why would they want to continue to inflict poorly maintained, unstable, and unsafe software on the world, under a well-known name that many people recognize and, sadly, still place too much trust in?
Posted Jul 28, 2016 16:17 UTC (Thu)
by ocrete (subscriber, #107180)
[Link] (1 responses)
Posted Aug 3, 2016 20:44 UTC (Wed)
by jospoortvliet (guest, #33164)
[Link]
The entire ecosystem around Foss office is less healthy thanks to this and users are harmed, getting far less than the best open source has to offer. Yeah it is frustrating, I can totally imagine that for the contributors to LO...
Posted Aug 4, 2016 15:01 UTC (Thu)
by moltonel (guest, #45207)
[Link]
Or for a slightly less snarky explanation: https://en.wikipedia.org/wiki/Escalation_of_commitment
Apache OpenOffice and CVE-2016-1513
Apache OpenOffice and CVE-2016-1513
Apache OpenOffice and CVE-2016-1513
Apache OpenOffice and CVE-2016-1513
Apache OpenOffice and CVE-2016-1513