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

[Feature Request]: Encryption #4

Open
lukehmcc opened this issue Aug 5, 2024 · 0 comments
Open

[Feature Request]: Encryption #4

lukehmcc opened this issue Aug 5, 2024 · 0 comments

Comments

@lukehmcc
Copy link
Member

lukehmcc commented Aug 5, 2024

Currently uploadBlob simply uploads the raw blob of the file to my s5 node. This is, ok, but for many use cases I don't want to have to trust my node. In order to upload, you already have to have an API instance with a seed, so encrypting based on that should be fine afaik (not an expert here).

When encrypting a file, it should also generate a unique decryption key so if I want to send the file in a link, I can include the decryption key alongside the CID so it's fully E2EE.

I know I could implement E2EE myself with public key encryption, but if it's most of the work is already done in the library, I feel like it makes more sense to do it there. Especially considering #3 and how decryption should be handled there.

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

1 participant