While this should really have been a concern of the PowerShell Execution Handler or the Azure-Pipelines-Task-Lib, it seems that a fix is needed until this is ported to where it belongs.
Closes #91.
Should also be fixed by configuring secure channel for .NET correctly on the server. But this seems to be what the official tasks are doing whether I like it or not.
While this should really have been a concern of the PowerShell Execution Handler or the Azure-Pipelines-Task-Lib, it seems that a fix is needed until this is ported to where it belongs.
Closes #91.
Should also be fixed by configuring secure channel for .NET correctly on the server. But this seems to be what the official tasks are doing whether I like it or not.