- Added: Paste copied to clipboard directories as soft links
- Added: Paste copied to clipboard files as hard links
- Added: License, features file, website shortcut
Note that shell icon overlays are not enabled by default because it may be an impact on shell performance. To enable, add a registry value that defines path patterns to be subject for digital signature verification.
Value Name: “Path Expressions”
Value: Comma-separated list of regular expression patterns, eg. “\.((exe)|(dll)|(cab))$” enables the feature for all .exe, .dll and .cab files.
Another handy shell extension for those who deal with digital signatures. The extension adds new columns to shell explorer and also allows to put digital signature related information into informational tooltips.
The following columns are added:
Some screenshots are shown below:
To add digital signature information info informational tip, use regedit to update the following items:
Key: HKEY_CLASSES_ROOT\dllfile, backup “InfoTip” value and append the following string:
This will add digital signature state, description and signing time to the tip. The same modification may be applied to HKEY_CLASSES_ROOT\exefile and other keys.
Keywords: CAPICOM, Shell Extensions, Digital Signatures, Authenticode
Some of you may be annoyed by the way signcode.exe keeps popping up the password prompt when trying to sign file from command line. There’s a workaround, however.
The utility catches password prompt and autoenters the password. After a minute of inactivity it quits. For use in bacth files like this:
start /b AutomateSigncodePassword.exe my-authenticode-password
signcode %1 -spc mycredentials.spc -v myprivatekey.pvk -t http://timestamp.verisign.com/scripts/timestamp.dll
Sometimes an automated update of the binary resource is required, to update version, product name, some custom string etc. We have an utility for this and and it found itsself being very useful.
We are unlikely to document it, I just leave a sample code illustrating how it all works.
Image = new ActiveXObject(“AlaxInfoResourceTools.Image”);
WScript.Echo(“Product Version: ” + Image.VersionInfo.ProductVersionString);
WScript.Echo(“File Version: ” + Image.VersionInfo.FileVersionString);
var ProductName = Image.VersionInfo.GetString(0, “ProductName”);
var OemProductName = Image.VersionInfo.GetString(0, “OemProductName”);
WScript.Echo(“ProductName: ” + ProductName);
WScript.Echo(“OemProductName: ” + OemProductName);
Image.VersionInfo.SetString(0, “OemProductName”, “// ” + ProductName);
Curious ones are invited to open type library to find out the syntax.
Download the COM object (265K) ResourceToolsSetup.msi (Win32, 32-bit)