Don't sign activate.ps1

[zmbq]

The PowerShell activation script is signed. This allows users set the PowerShell execution policy to AllSigned. On the other hand, it prevents the script from setting a user-specified prompt, requiring users to manually change the script instead of using the --prompt flag.

Unsigned scripts require the 'unrestricted' execution policy. I don't know any developer that hasn't set the execution policy to 'unrestricted' anyway, as it prevents the ability to run your own scripts.

So I suggest not signing the script, and supporting custom prompts.

[FranklinYu]

Unsigned scripts require the 'unrestricted' execution policy. I don't know any developer that hasn't set the execution policy to 'unrestricted' anyway, as it prevents the ability to run your own scripts.

To run a locally-written script, RemoteSigned is enough. This level only checks signature of scripts downloaded from Internet. My employer therefore have a group policy to enforce this level. I cannot change that locally. Oddly enough, Windows thinks activate.ps1 is remote script. (I can no longer reproduce this issue.)

[gaborbernat]

Fixed via #1258.