-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Password-protected AES-256 encrypted pastes #33
Comments
Stale issue message |
Stale issue message |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please check the box if you understand that this repo is only for server-side backend issues. Please write issues related to the frontend or cli client in their respective repositories:
Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
When pastes are uploaded, perhaps through a
/encrypt
endpoint, you would need to specify apassword
in the query parameters (or multipart form value). The server would then hash the password, salt it, encrypt the paste, and return the ID. No other data will be stored on the server other than the hash of the password.Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: