-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add support for use of secure strings for sensitive parameters #195
Comments
tenthirtyam
pushed a commit
to Ashwini-Ravi/powershell-module-for-vmware-cloud-foundation-reporting
that referenced
this issue
Dec 15, 2023
Added support for use of secure strings for sensitive parameters. Red: vmware#195 Signed-off-by: Ashwini Ravindernath <[email protected]>
tenthirtyam
pushed a commit
to Ashwini-Ravi/powershell-module-for-vmware-cloud-foundation-reporting
that referenced
this issue
Dec 15, 2023
Added support for use of secure strings for sensitive parameters. Ref: vmware#195 Signed-off-by: Ashwini Ravindernath <[email protected]>
11 tasks
tenthirtyam
pushed a commit
to Ashwini-Ravi/powershell-module-for-vmware-cloud-foundation-reporting
that referenced
this issue
Dec 15, 2023
Added support for use of secure strings for sensitive parameters. Ref: vmware#195 Signed-off-by: Ashwini Ravindernath <[email protected]>
tenthirtyam
pushed a commit
to Ashwini-Ravi/powershell-module-for-vmware-cloud-foundation-reporting
that referenced
this issue
Dec 15, 2023
Added support for use of secure strings for sensitive parameters. Ref: vmware#195 Signed-off-by: Ashwini Ravindernath <[email protected]>
tenthirtyam
pushed a commit
that referenced
this issue
Dec 15, 2023
Added support for use of secure strings for sensitive parameters. Ref: #195 Signed-off-by: Ashwini Ravindernath <[email protected]>
I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Code of Conduct
Description
For example: if one runs a command with no input one is prompted for:
server:
user:
password:
The password value should not be echo'd back to the screen in plaintext
Use Case(s)
A user may not want to reveal sensitive credentials during a screen sharing session.
Potential Configuration
Please consider the use of -AsSecureString when reading in the password interactively.
References
No response
The text was updated successfully, but these errors were encountered: