Unfortunately, the announcement has consequences for ownCloud, Inc. based in Lexington, MA. Our main lenders in the US have cancelled our credit. Following American law, we are forced to close the doors of ownCloud, Inc. with immediate effect and terminate the contracts of 8 employees. The ownCloud GmbH is not directly affected by this and the growth of the ownCloud Foundation will remain a key priority.
What worries me a bit is that afaik Frank was the owncloud maintainer while many of these vulns were introduced.
I’m not saying I believe he’s directly responsible, but a lot of that broken code was apparently committed under his watch.
Even if you restrict yourself to the stdlib, almost every builtin has gotchas that can introduce serious errors.
The documentation ranges from factual-but-unhelpful to misleading or outright inaccurate, with just enough moments of helpfulness to keep you reading.
I’m done with that ecosystem. Not willing to run php on networks I care about anymore - it’s too hard to get right.
It’s fairly common for founders to make room for technically more specialized people, and there is no single maintainer of ownCloud/Nextcloud. Lukas Reschke appears to be fairly competent in his field, so I guess they’ve got it under control by now.
Article from a news site, giving more context.
Here’s owncloud’s blog with the official announcement.
I am curious which American law requires them to close the doors immediately.
https://owncloud.com/owncloud-statement-concerning-formation-nextcloud-frank-karlitschek/
I’m also curious what’s going to happen with their domain – it says “© ownCloud, Inc. 2011-2016” at the bottom of their owncloud.com pages. Will it have to be sold off to their European company, following the approval from the lenders?
I hope the fork will do something about the constant stream of vulnerabilities as well. http://www.cvedetails.com/product/22262/Owncloud-Owncloud.html?vendor_id=11929
I had an owncloud instance running in 2014 but switched to plain webdav after having to upgrade owncloud every 2 weeks.
IIRC, there were also some scaling problems.
(Instead of ownCloud, I am completely insane and run SharePoint on my LAN instead.)
What worries me a bit is that afaik Frank was the owncloud maintainer while many of these vulns were introduced. I’m not saying I believe he’s directly responsible, but a lot of that broken code was apparently committed under his watch.
It’s stunningly hard to write secure code in PHP.
Even if you restrict yourself to the stdlib, almost every builtin has gotchas that can introduce serious errors. The documentation ranges from factual-but-unhelpful to misleading or outright inaccurate, with just enough moments of helpfulness to keep you reading.
I’m done with that ecosystem. Not willing to run php on networks I care about anymore - it’s too hard to get right.
It’s fairly common for founders to make room for technically more specialized people, and there is no single maintainer of ownCloud/Nextcloud. Lukas Reschke appears to be fairly competent in his field, so I guess they’ve got it under control by now.