Re:Pwncloud – Bad crypto in the Owncloud encryption module
by Semaphor on Monday April 11, 2016 @04:33AM
(#11470310)
What seems truly scary is how little the developer seemed to care about those security bugs (following related issues, you also find an exploit, SQL injection and so on) and being dismissive of the guy who found them.
[ Parent
| on HN ]
Re:Pwncloud – Bad crypto in the Owncloud encryption module
by embik on Monday April 11, 2016 @05:45AM
(#11470484)
https://github.com/haiwen/seafile/issues/587#issuecomment-40...
> We don't roll our own crypto.
> There are two parts of the code base in which "we roll our own crypto": the transfer protocl and encrypted library.
That's just ridiculous.
Re:Pwncloud – Bad crypto in the Owncloud encryption module
by JohnIcare on Monday April 11, 2016 @07:30AM
(#11470805)
For information : since that github comment, now the protocol relies only on HTTPS.
About metadata : https://seacloud.cc/group/3/wiki/seafile-roadmap.md there is one line saying "Ability to encrypt all data by server key. Key has to be generated by administrator" but it's not on the changelog page ( https://seacloud.cc/group/3/wiki/Server%20ChangeLog.md )