feat: e2e encription #31
Open
+480
−10
Conversation
This file contains hidden or 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
Author
|
@antonmedv I did a new PR only for the e2e encruption, without prettier formatter. Now I think it is more clear |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
How the e2e encription works:
AES-GCM 256-bit
Military-grade encryption standard.
Built-in data authentication.
PBKDF2 with 100,000 iterations
Secure key derivation from the password.
Protects against brute-force attacks.
Random Salt and IV
Each document has unique values.
Prevents rainbow table attacks.
Password Never Transmitted
The password remains only on the client side.
It is never included in the URL or stored in localStorage.
This is an optional feature that the user can enable in the menù