Update powershell code to use APIs that take SecureString when they become available in .NET Core #3228
Description
Metadata
Metadata
Assignees
Labels
The issue is fixed.The issue is fixed.core PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtimewaiting on a fix/change in .NETwaiting on a fix/change in .NET
Type
Fields
Give feedbackNo fields configured for issues without a type.
PowerShell Core currently uses some APIs that only take plain password text, because the overloads that take
SecureStringis not available in .NET Core. But once they become available, we need to update our code to switch to the latter.Instances: (not a complete list)
Constructor of
NetworkCredentialatCredential.csConstructor of
X509Certificate2inCertificateCommands.csProcessStartInfo.PasswordInClearTextat [Process.cs]Feel free to update this list when you spot one.