Removed Seafile #491

2018-07-03T10:25:25Z

ghost commented

2018-07-03 10:25:25 +00:00

(Migrated from github.com)

Description

Removed Seafile from both cloud storage providers and self hosted cloud storage. This is due to issues #465 and #490 - the encryption has large flaws and after 5 years, the developers seem to have no intent to fix this.

Under providers, bumped Muonium up to last space.

Under self hosted, bumped NextCloud up to last space.

Not having used anything other than NextCloud previously, I'm unsure of ordering - I'll leave this up to somebody else if there's a better order.

I also fixed the color of the button for Magic Wormhole.

HTML Preview

http://htmlpreview.github.io/?https://github.com/sevengali/privacytools.io/blob/master/index.html

### Description Removed Seafile from both cloud storage providers and self hosted cloud storage. This is due to issues #465 and #490 - the encryption has large flaws and after 5 years, the developers seem to have no intent to fix this. Under providers, bumped Muonium up to last space. Under self hosted, bumped NextCloud up to last space. Not having used anything other than NextCloud previously, I'm unsure of ordering - I'll leave this up to somebody else if there's a better order. I also fixed the color of the button for Magic Wormhole. ### HTML Preview http://htmlpreview.github.io/?https://github.com/sevengali/privacytools.io/blob/master/index.html

👍 2

RichardRMatthews commented

2018-07-03 17:25:59 +00:00

(Migrated from github.com)

Thank's for including my issue.

dakira commented

2018-08-15 08:39:41 +00:00

(Migrated from github.com)

@sevengali I really don't see the reason for this. The other proposed solutions don't offer client side encryption at all (Nextclouds solution is still in beta). As for the password hashing. That's just the matter of submitting a simple PR or issue. For the users where this matters (installations with many users) it usually shouldn't be a problem as they use other means of authentication in the first place (kerboros, shibboleth).

Looks to me like a hater on a crusade.

@sevengali I really don't see the reason for this. The other proposed solutions don't offer client side encryption at all (Nextclouds solution is still in beta). As for the password hashing. That's just the matter of submitting a simple PR or issue. For the users where this matters (installations with many users) it usually shouldn't be a problem as they use other means of authentication in the first place (kerboros, shibboleth). Looks to me like a hater on a crusade.

😆 1

digital-spinner commented

2018-08-26 08:22:16 +00:00

(Migrated from github.com)

@sevengali so the only issue is with the weak encryption? What about self hosted solution where the server itself is already LUKS encrypted (as a whole or partially) hosting and sharing my own and family stuff using HTTPS and 2factor authentication?

From my stand point of view this issue doesn't matter at all, also like @dakira said - other solutions do not have encryption at all? I have used the Seafile self hosting community version for more than 2 years now finding it so much easy to setup, backup and maintain compared to Nextcloud.. And the raw functionality is way way better then Nextcloud for me which crashed just a week after installation with about for 1TB of data. Also storing data looks a totally different in Seafile (using GIT fork as a backend) than Nextclud (are files still just dropped on the server?).. Replacing the Seafile with Nextcloud for it's base functionality is a step back IMO in terms of solution stability and easy of use.

Please reconsider this removal. BTW. IMO users wanting higher level of protection should encrypt their files transparently (eg. by Cryptomator) before using ANY cloud service.

@sevengali so the only issue is with the weak encryption? What about self hosted solution where the server itself is already LUKS encrypted (as a whole or partially) hosting and sharing my own and family stuff using HTTPS and 2factor authentication? From my stand point of view this issue doesn't matter at all, also like @dakira said - other solutions do not have encryption at all? I have used the Seafile self hosting community version for more than 2 years now finding it so much easy to setup, backup and maintain compared to Nextcloud.. And the raw functionality is way way better then Nextcloud for me which crashed just a week after installation with about for 1TB of data. Also storing data looks a totally different in Seafile (using GIT fork as a backend) than Nextclud (are files still just dropped on the server?).. Replacing the Seafile with Nextcloud for it's base functionality is a step back IMO in terms of solution stability and easy of use. Please reconsider this removal. BTW. IMO users wanting higher level of protection should encrypt their files transparently (eg. by Cryptomator) before using ANY cloud service.

dakira commented

2018-08-26 10:55:56 +00:00

(Migrated from github.com)

@Shifterovich see above

ghost commented

2018-08-26 22:07:17 +00:00

(Migrated from github.com)

@kewde thoughts?

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#491