Powershell trick #1 - checking binary signatures
I love Monad Powershell.
I have been using Powershell lately and it has really made my job easier. It provides a quick and easy way to work with certificates, XML, etc. I'd like to share some of the tricks that I use.
Useful Trick #1 - Checking the signature of a binary.
Type this at the PSH prompt:
$(get-AuthenticodeSignature myfile.exe).SignerCertificate.Subject
It will show you the Subject name on the certificate that signed the file, if it is signed. You can use this to do lots of things, like verifying that all of your files are signed before you ship them. You can also use set-AuthenticodeSignature to sign files, although I have not experimented with this.
Comments
- Anonymous
March 02, 2006
What does this do over, the 'ol
Right click on the file, Properties, select the Digital Signatures tab?
scriptable i guess, handy for final checks before a release. - Anonymous
March 02, 2006
It's programmatic, it scales to a large number of files, and it's much less of a pain. No need to open up an explorer window, dig around in the directory.. - Anonymous
March 03, 2006
Has anyone figured out how to change the Monad namespace over ActiveSync. After all, since Monad can already treat the registry and WMI stores as namespaces, an ActiveSync attached device should be doable. - Anonymous
March 03, 2006
I think that is possible but you'd have to write the provider for the sync transport. The "Explore" feature of ActiveSync doesn't offer a real fully-featured filesystem (notice that you can't mount the drive). I would love to have a provider for the attached device though. - Anonymous
March 03, 2006
I too use Monad and Windows Mobile, and I'd love to be able to get to my files through Monad!
Please, someone make a Provider!! - Anonymous
May 11, 2006
The comment has been removed