v0.2

NoInk.ps version 0.2

Description

The signed version of the NoInk.ps Powershell script.

What's new:

• Added two new optional parameters: -ShowAll and -DryRun
• Better and more verbose output with a more clear description of what is going on
• Some ink annotations that not always were removed are removed correctly now
• Some typos corrected, better comments

Notes

Attached to this release you can find the signed version of the script that gives you the following advantages:

• Assurance that the script hasn't been modified
• If you set your policy to AllSigned or RemoteSigned it will execute

You can verify the signature using the following command:

Get-AuthenticodeSignature .\NoInk.ps1 | Format-List

check that the Subject and the Issuer fields are like the following:

[Subject]
E=msz@msz.eu, CN="Open Source Developer, Marco Zuppone", O=Open Source Developer, L=Reading, S=Berkshire, C=GB
[Issuer]
CN=Certum Code Signing CA SHA2, OU=Certum Certification Authority, O=Unizeto Technologies S.A., C=PL

v0.1.1

NoInk.ps version 0.1.1

Description

The signed version of the NoInk.ps Powershell script.

What's new:

Some typos corrected, better comments.

Notes

Attached to this release you can find the signed version of the script that gives you the following advantages:

• Assurance that the script hasn't been modified
• If you set your policy to AllSigned or RemoteSigned it will execute

You can verify the signature using the following command:

Get-AuthenticodeSignature .\NoInk.ps1 | Format-List

check that the Subject and the Issuer fields are like the following:

[Subject]
E=msz@msz.eu, CN="Open Source Developer, Marco Zuppone", O=Open Source Developer, L=Reading, S=Berkshire, C=GB
[Issuer]
CN=Certum Code Signing CA SHA2, OU=Certum Certification Authority, O=Unizeto Technologies S.A., C=PL

First Signed Release

NoInk.ps version 0.1 -- Initial release

The signed version of the NoInk.ps Powershell script.

Notes

Attached to this release you can find the signed version of the script that gives you the following advantages:

• Assurance that the script hasn't been modified
• If you set your policy to AllSigned or RemoteSigned it will execute

You can verify the signature using the following command:

Get-AuthenticodeSignature .\NoInk.ps1 | Format-List

check that the Subject and the Issuer fields are like the following:

[Subject]
E=msz@msz.eu, CN="Open Source Developer, Marco Zuppone", O=Open Source Developer, L=Reading, S=Berkshire, C=GB
[Issuer]
CN=Certum Code Signing CA SHA2, OU=Certum Certification Authority, O=Unizeto Technologies S.A., C=PL