Skip to content

Update powershell code to use APIs that take SecureString when they become available in .NET Core #3228

@daxian-dbw

Description

@daxian-dbw

PowerShell Core currently uses some APIs that only take plain password text, because the overloads that take SecureString is 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 NetworkCredential at Credential.cs
Constructor of X509Certificate2 in CertificateCommands.cs
ProcessStartInfo.PasswordInClearText at [Process.cs]

Feel free to update this list when you spot one.

Metadata

Metadata

Assignees

Labels

Resolution-FixedThe issue is fixed.WG-Enginecore PowerShell engine, interpreter, and runtimeWaiting - DotNetCorewaiting on a fix/change in .NET

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions