Digitally sign tsp.ps1

[archerzz]

Clear and concise description of the problem

I met the following error when trying to install vs code plugin for typespec.

PS C:\Users\xxx> tsp code install
tsp : File C:\Users\xxx\AppData\Roaming\npm\tsp.ps1 cannot be loaded. The file
C:\Users\xxx\AppData\Roaming\npm\tsp.ps1 is not digitally signed. You cannot run this script on the current
system. For more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ tsp code install
+ ~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

It would be better if we could digitally sign tsp.ps1. Otherwise, customers have to downgrade the execution policy.

---

My local execution policy is set to AllSigned by default.

Checklist

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[timotheeguerin]

This is not created by us, where did you get this ps1 file?

[bterlson]

This is likely the PS1 wrapper generated by npm on windows and placed in the bin folder. I don't think we can do anything to sign it.

[timotheeguerin]

Issue from npm npm/cli#470 about this

[archerzz]

This is likely the PS1 wrapper generated by npm on windows and placed in the bin folder. I don't think we can do anything to sign it.

Thanks. Per conclusion of solutions here, looks like we need to add a doc to let users delete the tsp.ps1?

[timotheeguerin]

I don't think so, the conclusion is to loosen the script execution policy or use npx. And not sure this is really for us to show the docs on this

[archerzz]

close since there is no easy solution for that