From 01de64c1da316fdce497dad6dc27fb8dd5bd8e88 Mon Sep 17 00:00:00 2001 From: Edward Delaporte Date: Mon, 8 Feb 2021 17:34:14 -0600 Subject: [PATCH] Add usage examples. --- psmodules/sign.psm1 | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/psmodules/sign.psm1 b/psmodules/sign.psm1 index a5667de..3a017a6 100644 --- a/psmodules/sign.psm1 +++ b/psmodules/sign.psm1 @@ -3,6 +3,31 @@ Commands to maintain a local code singing cert. +This is a hack to solve allowing PowerShell to trust a PowerShell profile hosted on a UNC path, without allowing 'Unrestricted' execution policy. + +I created this because it annoys me that my mandatory UNC path profile counts as a remote script, and I'm too pedantic to un-restrict all remote scripts just to allow my profile to load. + +.NOTES + +Works fine under PowerShell Core 6 with ExecutionPolicy RemoteSigned. PowerShell 7 + +.EXAMPLE + +Set-ExecutionPolicy RemoteSigned + +Import-Module c:\src\dotfiles\psmodules\sign.psm1 + +# Make a cert + +> New-CodeSignCert +# Install it - you will be promted whether to trust it. + +> Install-CodeSignCert + +# Sign your UNC path PowerShell profile +> Invoke-CodeSign $profile + + #> $certName = "Local Code Sign Cert" $codeSigning = "" -- 2.47.3