Wilson Mar bio photo

Wilson Mar

Hello. Hire me!

Email me Calendar Skype call 310 320-7878

LinkedIn Twitter Gitter Google+ Youtube

Github Stackoverflow Pinterest

I am who I say I am because my CA says so


Overview

This article describes the use of self-signed code signing certificates on Microsoft Windows operating systems.

Kleopatra UI

See https://www.deepdotweb.com/2015/02/21/pgp-tutorial-for-windows-kleopatra-gpg4win/

Create self-signed cert on Windows

Based on http://www.hanselman.com/blog/SigningPowerShellScripts.aspx

  1. On Windows machines, in directory “C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin" invoke the makecert.exe GUI.

  2. Setup a Certificate Authority (CA):

    
    makecert -n "CN=PowerShell Local Certificate Root" -a sha1 -eku 1.3.6.1.5.5.7.3.3 -r -sv root.pvk root.cer -ss Root -sr localMachine
    
    
    
  3. Type in a Password twice for the Subject Key.

  4. Type it in again.

    See the cert under “Trusted root CA”.

  5. Generates a personal certificate from the above certificate authority:

    
    makecert -pe -n "CN=PowerShell User" -ss MY -a sha1 -eku 1.3.6.1.5.5.7.3.3 -iv root.pvk -ic root.cer   
    
  6. Type in a password for the Issuer Signature.

    See the cert under Personal.

  7. Invoke mmc.exe, and add the Certificates snap-in for “My user account” to view certificates.

  8. Verify the certificate is known within PowerShell:

    
    Get-ChildItem cert:\CurrentUser\My -codesign   
    
  9. Delete in your working directory temporary files root.pvk and root.cer.

    The certificate info is stored with that of others, in “C:\Documents and Settings[username]\Application Data\Microsoft\SystemCertificates\My".

  10. Sign a script, replacing “c:\foo.ps1” with the full path to your script:

    Set-AuthenticodeSignature c:\foo.ps1 @(Get-ChildItem cert:\CurrentUser\My -codesign)[0]

  11. Use a text editor to view the script, which now has a signature block that begins with:

    # SIG # Begin signature block"
    

Export for running elsewhere

PROTIP: When sending a script, also send along its Powershell certificates in the Trusted Root Certification Authorities container.
Also send the Trusted Publishers file to prevent the first-time prompt from appearing.

  1. Right-click and select Export for the Certificate Export Wizard GUI.

  2. Leave “DER encoded binary X.509 (.CER)” selected and click Next.

  3. Specify the file name after a full path and click Next.

    PROTIP: It helps if everyone in an organization makes use of a company-standard folder.

  4. Click Finish.

  5. Click OK to the “The export was successful” pop-up.

    Verify a signed script can be used

  6. Set

    Set-ExecutionPolicy AllSigned

More on DevOps

This is one of a series on DevOps:

  1. DevOps_2.0
  2. User Stories for DevOps

  3. Choices for DevOps Technologies
  4. Java DevOps Workflow
  5. AWS DevOps (CodeCommit, CodePipeline, CodeDeploy)
  6. AWS server deployment options

  7. Digital Ocean
  8. Cloud regions
  9. AWS Virtual Private Cloud
  10. Azure Cloud Powershell

  11. Git and GitHub vs File Archival
  12. Git Commands and Statuses
  13. Data Security GitHub
  14. Git Commit, Tag, Push
  15. Git Utilities
  16. GitHub API

  17. TFS vs. GitHub

  18. Jenkins Server Setup
  19. Jenkins Plug-ins
  20. Jenkins Freestyle jobs
  21. Jenkins2 Pipeline jobs using Groovy code in Jenkinsfile

  22. Dockerize apps
  23. Docker Setup
  24. Docker Build

  25. Maven on MacOSX

  26. Powershell Ecosystem
  27. Powershell on MacOS
  28. Powershell Desired System Configuration

  29. Ansible

  30. MySQL Setup

  31. SonarQube static code scan

  32. API Management Microsoft
  33. API Management Amazon

  34. Scenarios for load