-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Description
This would not be "secure" encryption. This would just be a local VSCode-level hashing or obfuscation of the password. The main goal here is for me to be able to show new developers how the target.secret.properties files work, or record training videos about it, without having to show my password on a screen share. It'll also make people feel better to not have the possibility to check in their password.
So my thinking is it would work like this:
- Create a new command that will prompt the user for a value to obfuscate
- If an obfuscation key does not exist, generate a random 'passphrase' and store it in the User level VSCode settings
- Use the passphrase to encrypt the value and return a Base64 string to the user (or insert it at the cursor). Prefix with a known value, such as 'obf:' to ensure that we decode it when needed
- Whenever we need the %%ECLIPSE_PASS%%, decode it and store it in the plugin as we do today
Metadata
Metadata
Assignees
Labels
No labels