Remove ReadLineSafe from known issues

This commit is contained in:
Andrew Schwartzmeyer 2016-07-05 15:24:44 -07:00
parent 50e31e68bb
commit 53a3b760cd
2 changed files with 1 additions and 14 deletions

View file

@ -1,18 +1,5 @@
# Known Issues
## SecureString
The `SecureString` class is *not* the well-known C# `SecureString`, as the
library is not available in .NET Core. However, PowerShell continues to use the
type for two main reasons: FullCLR compatibility, and as a specially-treated
type (that is, behavior is dependent on the type being `SecureString`). Instead,
the `SecureString` is Mono's completely not secure whatsoever, but open-source
and "compatible" stub that acts just like a plaintext `StringBuilder`. **It has
no encryption.**
Additionally `ReadLineSafe` is not implemented, meaning `Get-Credential` fails
with `PlatformNotSupportedException`.
## Files excluded from the build
#### Microsoft.PowerShell.Commands.Management

View file

@ -299,7 +299,7 @@ namespace Microsoft.PowerShell
StringBuilder result = new StringBuilder();
#if LINUX
bool treatControlCAsInput = Console.TreatControlCAsInput;
#endif
#else
ConsoleHandle handle = ConsoleControl.GetConioDeviceHandle();
ConsoleControl.ConsoleModes originalMode = ConsoleControl.GetMode(handle);
bool isModeChanged = true; // assume ConsoleMode is changed so that if ReadLineSetMode