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.

Sign up for GitHub

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

Jump to bottom

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

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

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

cyberduck opened this issue May 7, 2014 · 13 comments
Assignees
@dkocher
Labels
cryptomator Cryptomator Vault enhancement fixed
Milestone
6.0

Comments

@cyberduck
Copy link
Collaborator

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

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 ?

@cyberduck
Copy link
Collaborator Author

023e870 commented

Hello David,

Is there any blue prints or any target about that ?

Thanks,

Cédric

@cyberduck
Copy link
Collaborator Author

@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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8628 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

f19f995 commented

is there any near future plans for client side encryption?

@cyberduck
Copy link
Collaborator Author

@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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Our implementation will be based on and interoperable with Cryptomator.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Forthcoming documentation on this wiki page.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In between 280ed39 and 22814.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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

@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.
Assignees

@dkocher dkocher

Labels
cryptomator Cryptomator Vault enhancement fixed
Projects
None yet
Milestone
6.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck