-
Notifications
You must be signed in to change notification settings - Fork 302
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: decrypt only / restrict who can encrypt? #1635
Comments
+1 on this, to expand on a use case, this would prevent the tool being abused as a phising vector Eg. malicious actor encrypts a message with malware download link etc, then uses the encrypted message hosted on the companies portal to look legit |
fwiw we made some modifications to the code to make a unique URI/location for the encrypt (CreateSecret and Upload) as a workaround solution for now. Probably not fully obfuscated, but makes it more difficult (these are example GUIDs and not the ones I actually used): in website/src/Routing.tsx:
|
+1 would love this! |
I successfully deployed yopass to S3/Lambda - but was wondering - is there an easy method of restricting who can encrypt new secrets while allowing anyone to decrypt?
The text was updated successfully, but these errors were encountered: