Aditya Patwardhan 7dfcff9287 Merged PR 9168: Disable Enter-PSHostProcess cmdlet when system in lock down mode ... This is based on an issue, where Enter-PSHostProcess on a locked down (WDAC enforced) machine allows any admin to connect to any another local hosted PowerShell process and execute commands as that user. This amounts to privilege escalation on the policy locked down machine and something we want to prevent. Fix is to check for system lock down and disable Enter-PSHostProcess cmdlet with an error message.		2019-07-16 00:49:24 +00:00
..
Modules	Update tests to account for when $PSHOME is readonly (#9279)	2019-04-04 23:01:01 -07:00
TestData/CatalogTestData
AclCmdlets.Tests.ps1
AmsiInterface.Tests.ps1
certificateCommon.psm1	Update use of "PowerShell Core" to just "PowerShell" (#9513)	2019-05-10 15:34:27 -07:00
CertificateProvider.Tests.ps1
CmsMessage.Tests.ps1
ConstrainedLanguageDebugger.Tests.ps1	Disable the debugger when in system lock-down mode (#9645)	2019-05-22 15:19:23 -07:00
ConstrainedLanguageModules.Tests.ps1
ConstrainedLanguageRestriction.Tests.ps1	Merged PR 9168: Disable Enter-PSHostProcess cmdlet when system in lock down mode	2019-07-16 00:49:24 +00:00
ConstrainedLanguageValidation.Tests.ps1
ExecutionPolicy.Tests.ps1	Multiple test fixes and improved logging for fragile tests (#9569)	2019-05-10 10:56:12 -07:00
FileCatalog.Tests.ps1	Update use of "PowerShell Core" to just "PowerShell" (#9513)	2019-05-10 15:34:27 -07:00
GetCredential.Tests.ps1
SecureString.Tests.ps1	Enable SecureString cmdlets for non-Windows (#9199)	2019-03-23 10:11:05 -07:00