-
Notifications
You must be signed in to change notification settings - Fork 791
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 v3 #87
Closed
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
For some reason, this was working untill I added a call to X509_REQ_get_subject_name, then the linking suddenly stopped working (even tougth I'm using a ton of other OpenSSL calls) Force to link against 1.0
I still need to send it to the server. It's been a long learning with the OpenSSL library.
Store it on memory, and discard it as soon as no longer needed.
There's something wrong on the CSR job that I need to discover.
finally. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org>
Enter a string list, return a string.
beware, this is broken.
We changed the name.
If we manage to encrypt and upload the private key to the server, the client is in it's connected state.
This new job sets the Encryption Flag in a folder.
- change the name of one Qt Message Handler - changed parameter from int to QString
This is already being called from somwhere else.
Since those networkjobs are all about client side encryption, mvoe them to clientsideencryption.h This will help with fewer conflicts with the origin.
Because nobody deservers to deal with Qt's JSON API
- TODO: Fix the incorrect "filename has been removed" popup. The file is not removed, just the popup shows.
Android only creates the metadata file when the first encrypted file is added. We assumed it would be there. This hacky code makes us store the metadata if there wasn't any yet. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
See nextcloud/end_to_end_encryption_rfc#13 Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
If the code was not complex enough syncing two tables already started to give UNIQUE constrains errors on simple sync operations, this also adds initial support remote delete of an encrypted file
This has no use outside of the clientsidenecryption.cpp
…into clientSideEncryptionV3
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.
Done:
In Progress:
Not Started:
Download
Handle the metadata
setup the encrypted file for upload (luckly there will be no changes in the uploader itself)
finish upload, unlock folder.
Currently Completely Missing:
TODO: