MSLab icon indicating copy to clipboard operation
MSLab copied to clipboard

Execution Policy / Signing

Open FlorianHeigl opened this issue 3 years ago • 4 comments

Please, could you somehow sign the scripts? The whole powershell signing premise makes no sense if there's no way to run signed code from microsoft. Opensource or not, isn't there some way?

FlorianHeigl avatar Jul 20 '22 21:07 FlorianHeigl

@machv can we sign it?

jaromirk avatar Jul 23 '22 11:07 jaromirk

Work in progress :-) I have my own personal code signing certificate, but I would prefer to sign the scripts with a corporate one, I am investigating what would be the best way to proceed.

let's keep this one open.

machv avatar Jul 23 '22 12:07 machv

@machv bless you!

FlorianHeigl avatar Jul 24 '22 20:07 FlorianHeigl

Hello @FlorianHeigl, it took me little bit longer than I expected, but in the latest release (v22.09.1) all PowerShell scripts in the ZIP file are now signed with Microsoft code signing certificate.

Please keep in mind that any change to LabConfig.ps1 file will render its signature invalid and you'll need to sign LabConfig.ps1 with your own certificate as LabConfig.ps1 is dot-sourced in main MSLab scripts and needs to be signed as well. I put this info also to README.

machv avatar Sep 30 '22 12:09 machv

You guys deserve hero hats for this! Exemplary that you didn't chicken out but were helpful and worked with your orgs processes to do the right thing!

Jaromir Kaspar @.***> schrieb am Di., 29. Nov. 2022, 15:29:

Closed #513 https://github.com/microsoft/MSLab/issues/513 as completed.

— Reply to this email directly, view it on GitHub https://github.com/microsoft/MSLab/issues/513#event-7913161004, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVSVGZV3H24PDLW5W3NKZDWKYHOBANCNFSM54FGWX2Q . You are receiving this because you were mentioned.Message ID: @.***>

FlorianHeigl avatar Nov 29 '22 14:11 FlorianHeigl