maxmustermann/PowerShell
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
PowerShell/test
History
Steve Lee 3255d84627 Enable SecureString cmdlets for non-Windows (#9199) 
On Unix systems, fallback to plaintext manipulation instead of using the DPAPI which is not available.

## PR Context

Currently, existing scripts that use SecureString cmdlets fail with an error complaining about crypt32.dll not being available.  This change allows these cmdlets to be used, but there is no encryption of the string.
.Net already [states](https://docs.microsoft.com/en-us/dotnet/api/system.security.securestring?view=netcore-2.1#remarks) that the contents of a SecureString are not encrypted on .Net Core.

Fix https://github.com/PowerShell/PowerShell/issues/1654

Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
2019-03-23 10:11:05 -07:00
..
common/markdown Update markdown test dependencies (#9075) 2019-03-09 08:30:14 +05:00
docker/networktest Remove appveyor functions from New-DockerTestBuild.psm1 (#8756) 2019-01-31 11:15:31 -08:00
hosting Update version for PowerShell.Native and hosting tests (#8983) 2019-03-04 11:08:19 -08:00
packaging/windows Remove extra AppVeyor environment check (#8709) 2019-02-08 10:57:41 -08:00
powershell Enable SecureString cmdlets for non-Windows (#9199) 2019-03-23 10:11:05 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Adding CmdletsToExport and AliasesToExport to test module manifests. (#9108) 2019-03-18 11:09:05 +05:00
xUnit Cleanup style issues in CoreAdapter and MshObject (#9190) 2019-03-23 09:52:30 +05:00
README.md Move xUnit tests in new folder (#8356) 2018-12-13 14:22:07 -08:00
Test.Common.props Removing Hardlink from Mode property in default file system format (#8789) 2019-03-12 15:49:16 -07:00

README.md

Testing

The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./xUnit. The third-party shebang test is in ./shebang.