Re:Pwncloud – Bad crypto in the Owncloud encryption module
by schlowmo on Sunday April 10, 2016 @07:01PM
(#11468616)
If you want to go along with owncloud (and I don't know a proper alternative) there's not much you can do then upgrading to Owncloud 9 and hope that the fix was done right. In the meantime you could encourage your users to use their own client-side encryption while giving up the idea of an easy setup.
[ Parent
| on HN ]
Re:Pwncloud – Bad crypto in the Owncloud encryption module
by nickik on Sunday April 10, 2016 @08:02PM
(#11468822)
Im already running the newest version. I hope they approve on it in future versions. Client side crypto would be cool.
Re:Pwncloud – Bad crypto in the Owncloud encryption module
by BjoernSchiessle on Monday April 11, 2016 @05:40AM
(#11470476)
There are some community activities to implement client-side encryption. But as far as I know there doesn't exists any running code at the moment. So don't expect to much in the next few months.
In general I want to note that client side encryption is great. I also like and use it in many areas. But you also have to keep in mind that it will make most of the web interface and it features useless. Personally I run my ownCloud in my basement. The connection to the server is secured by https and the hard disc is encrypted with LUKS. In this case it doesn't make sense to me to add additionally server-side or client-side encryption.
The first step is always to check your threat model, your setup and your requirements to see if you really need server-/client-side encryption.
Re:Pwncloud – Bad crypto in the Owncloud encryption module
by ultra2d on Monday April 11, 2016 @03:41AM
(#11470146)
Someone is working on that. It's called ownCrypt: https://github.com/owncloud/client/issues/4327 and
https://conference.owncloud.org/conference/oCC2015/proposal/...