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.

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

Encryption key should be handled only by the browser #415

Open
neuhaus opened this issue Nov 3, 2024 · 2 comments
Open

Encryption key should be handled only by the browser #415

neuhaus opened this issue Nov 3, 2024 · 2 comments

Comments

@neuhaus
Copy link
Contributor

neuhaus commented Nov 3, 2024

Right now, the server could be modified to save an unencrypted version of the password.

I'm suggesting to instead create the encryption key in the client, encrypt and decrypt in the client.

The encryption key would be transported in the fragment part of the URL following the hash sign that never gets sent to the server.

That's also how it's done in cryptpad.

@neuhaus
Copy link
Contributor Author

neuhaus commented Nov 12, 2024

I found another project that does it this way: https://privatebin.info/

@yurushao
Copy link
Contributor

The encryption key would be transported in the fragment part of the URL following the hash sign that never gets sent to the server.

Yeah this is a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants