New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't sign activate.ps1 #816

Closed
zmbq opened this Issue Nov 4, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@zmbq
Copy link

zmbq commented Nov 4, 2015

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

This comment has been minimized.

Copy link

FranklinYu commented Sep 17, 2018

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

This comment has been minimized.

Copy link
Contributor

gaborbernat commented Dec 18, 2018

Fixed via #1258.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment