Adding encrypted client #138
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the patch, but I'd rather not add a client for an encryption scheme not defined in a WebDAV-related RFC. I'd suggest to keep this in a separate repository instead :) |
|
Fair enough |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft and not done. I'm just checking if this is interesting.
I personally use WebDav using e2e encryption for storing data on my personal server. I use rclone for this, but rclone is lacking since it only supports symmetric encryption. With symmetric only, it couldn't be extended to support e2e Caldav or e2e Carddav where someone sends e2e calendar events to you.
This is a draft to show how I was intending to add e2ee support. If there is interest, I will finish the PR.