Repository navigation
Update powershell code to use APIs that take SecureString when they become available in .NET Core #3228
Description
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.
Activity
SteveL-MSFT commentedon Feb 28, 2017
Related #3198
#1654
CoreFx PR exposing SecureString dotnet/corefx#13362
mirichmo commentedon Mar 2, 2017
Should this be part of #3235?
daxian-dbw commentedon Mar 2, 2017
This one is related to security. I thought it probably would have higher priority and thus kept them separate.
daxian-dbw commentedon Apr 17, 2017
Fixed via #3556
iSazonov commentedon Apr 18, 2017
Joey Aiello (@joeyaiello) Please clarify - should we remove "Waiting-NetStandard20" if an Issue was fixed?
Now (after moving to .Net Core 2.0 in #3556) could we reuse the Label to mark Issues where we are waiting external bug fixes in CoreFX and CoreCLR?