Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client side encryption; Create encrypted vault interopable with Cryptomator #7937

Closed
cyberduck opened this issue May 7, 2014 · 13 comments
Closed

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 7, 2014

023e870 created the issue

Hi!

It would be great if the encryption of uploaded files could be done on the client side by CyberDuck, pros :

  • more secure form the client point of view
  • unload the server, the client do all the encryption task
  • can be used with S3 compatible hosting platform that do not support server side encryption (like Ceph, and others)
  • could be protocol agnostic

Questions :

  • in the way the option could be enable or disable for each upload or sync, how to recognize encrypted and non encrypted files at the download time ? adding a .gpg suffix to all encrypted files could do the job.

Thanks for any further suggestions.

Cédric

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 7, 2014

023e870 commented

Maybe gpg is not the better choice to do it : third party software are needed and key management could be a pain for neophyte users. What about AES ?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 20, 2014

023e870 commented

Hello David,

Is there any blue prints or any target about that ?

Thanks,

Cédric

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 20, 2014

@dkocher commented

Replying to [comment:3 dafresh]:

Hello David,

Is there any blue prints or any target about that ?

No, I have no immediate plans for this feature. Patches are welcome.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 3, 2015

@dkocher commented

#8628 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 15, 2015

f19f995 commented

is there any near future plans for client side encryption?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 15, 2015

@dkocher commented

Replying to [comment:6 aivaras.sukackas]:

is there any near future plans for client side encryption?
No, this feature is not currently scheduled in a milestone.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 22, 2016

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 19, 2016

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 3, 2016

@dkocher commented

Our implementation will be based on and interoperable with Cryptomator.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 3, 2016

@dkocher commented

Forthcoming documentation on this wiki page.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 8, 2016

@dkocher commented

In between 280ed39 and 22814.

Loading

@cyberduck cyberduck closed this Dec 8, 2016
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 11, 2017

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 26, 2017

@dkocher commented

https://blog.cyberduck.io/2017/01/19/cryptomator/
You can give the Cryptomator vault support a try in the current beta builds.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants