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

Is encryption planned? #1258

Open
foozzi opened this issue Mar 4, 2023 · 5 comments
Open

Is encryption planned? #1258

foozzi opened this issue Mar 4, 2023 · 5 comments

Comments

@foozzi
Copy link

foozzi commented Mar 4, 2023

AES-256/CHACHA20?

@boojack
Copy link
Collaborator

boojack commented Mar 7, 2023

What part of the content needs to be encrypted? memo's content?

@foozzi
Copy link
Author

foozzi commented Mar 16, 2023

What part of the content needs to be encrypted? memo's content?

Yes, memo's content

@foozzi foozzi closed this as completed Mar 29, 2023
@ymstnt
Copy link

ymstnt commented Apr 3, 2023

Why was this closed?

Was this implemented? Doesn't seem to be the case, unless I'm mistaken.

An optional database encryption would be useful, it could prevent an attacker from reading the memo's content in case of a badly configured system or breach.
Or just preventing the instance provider from reading private memo's content, so users could rest easily knowing their secrets are encrypted.

@okainov
Copy link

okainov commented Sep 3, 2024

Also not sure, why was this closed? See also #2161 #1480 which are closed without comments. @boojack could you please clarify the direction here?

@albotroz
Copy link

I also wonder why this feature suggestion of all things is constantly being closed.

@foozzi foozzi reopened this Nov 17, 2024
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

5 participants