{"id":33,"date":"2017-06-18T12:55:33","date_gmt":"2017-06-18T16:55:33","guid":{"rendered":"http:\/\/ziviz.us\/WP\/?p=33"},"modified":"2017-06-18T13:01:47","modified_gmt":"2017-06-18T17:01:47","slug":"powershell-signing","status":"publish","type":"post","link":"https:\/\/www.ziviz.net\/WP\/2017\/06\/18\/powershell-signing\/","title":{"rendered":"PowerShell Signing"},"content":{"rendered":"

This post was migrated from my older blog.<\/em><\/p>\n

I wanted to sign a PowerShell script to make it easier and more secure to use in our environment. PowerShell signing was not in great use in the environment. To make signing the scripts easier I created a simple script<\/a> to help with the signing process. There was an issue however. We have generic, fully trusted, all purposes certificates. Despite being fully trusted and all purpose, they did not show up as valid certificates in PowerShell. I tried manually running:<\/p>\n

Get-ChildItem cert:\\CurrentUser\\My -codesigning<\/code><\/pre>\n
It returned nothing. The certificates should work, but they weren’t showing up. I checked the certificate inside of the Certificate Store. Inside the certificate’s properties on the “General” tab, there is a “Certificate purposes” group box. Inside of this “Enable all purposes for this certificate” was selected.<\/p>\n
\"CertStore\"
Showing how to manually enable all purposes<\/figcaption><\/figure>\n
Since that was not working, I selected “Enable only for the following purposes”.
\nBy default, all purposes were already checked. I clicked “Ok” and ran the Get-ChildItem command again and the certificate was finally listed. I ran through the signing process successfully. The signature on the PowerShell file was trusted and valid.<\/p>\n","protected":false},"excerpt":{"rendered":"
This post was migrated from my older blog. I wanted to sign a PowerShell script to make it easier and more secure to use in our environment. PowerShell signing was not in great use in the environment. To make signing the scripts easier I created a simple script to help with the signing process. There … Continue reading “PowerShell Signing”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4],"tags":[],"class_list":["post-33","post","type-post","status-publish","format-standard","hentry","category-code-release","category-powershell"],"_links":{"self":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/33","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/comments?post=33"}],"version-history":[{"count":4,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/33\/revisions"}],"predecessor-version":[{"id":183,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/33\/revisions\/183"}],"wp:attachment":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/media?parent=33"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/categories?post=33"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/tags?post=33"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}