-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Burn after read & encryption problem #50
Comments
Will look into the first issue, thanks for the report.
That's an inherent property: those random characters are the key to decrypting the messages since it's not being stored in the server. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have issue with"burn after read" as when it's checked, the file opens immediately upon saving on the current page, making it impossible for anyone other than the author to read it because the link expires right after creation. The second issue is that if "encrypted" is checked and the password isn't entered, a lot of random characters appear in the link. In my opinion, there should be an option for default disabling of this for EVERYONE rather than in the settings for just one user, for example, the option to disable it would be in the .env or Docker config.
The text was updated successfully, but these errors were encountered: