Client side encryption #20
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
Call the apps api and check if the response has the client_side_encryption key. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org>
If the server supports client syde encryption, display a menu on right click that should display encrypt and decrypt. ideally it would show the encrypt if the folder is decrypted, and decrypt if the folder is encrypted but currently there's no way for the client to know that.
File id is a must if we want to call any API. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org>
This way we can actually request the id from outside of the model.
This network job does a DELETE http request on a URL. It's the second class that does basically the same, but this one returns the http return code, and it's set to do a api call.
If the server allows client side encryption, show the user the menu with the encrypt and unencrupt options
This will be the responsible for encryption, decryption and talking with the server.
This is the first step needed to properly communicate. Next, get private key.
Not stored anywhere yet, but it's correctly running.
Now I need to understand what the hell I need to do to send this to the server.
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.
It does not really belong in the discoveryphase.h as it is used also for propagator option. Also use C++11 style member initializer
…etwork job Remove one dependency from the config file for the sync engine. Part of issue #6213
it's a network job after all
The request for folders whas also replying for files.
Parts of the code are indented by spaces, other parts by tabs. This needs to run in the whole codebase.
The upload is made in an event loop with more than one upload at the same time, this confuses the hell out of the folder locking mechanism. We need to lock the folder and ask the other trials to try again in a few seconds in the future to give time for the uploader to actually upload the current file that's locking the folder.
So we can unlock it later. - perhaps we should store this on the disk or something, to make it harder to lose.
This broke when we started to use QSslKey and the Qt Keychain framework.
Move config and remove most dependencies form the sync engine.
This makes sure the folder will be unlocked for next tests
8 tasks
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.
No description provided.