Signotaur can be used to verify the signatures of ClickOnce deployments and VSTO (Visual Studio Tools for Office) add-ins by checking the deployment manifest (.application or .vsto), application manifest (.manifest), and all dependency files.
When you verify a .application or .vsto file, Signotaur automatically checks:
.vsto file signatures.Any mismatch in the hash chain or invalid signature will cause verification to fail.
By default, all dependencies are verified. You can use content patterns to selectively verify only specific files or exclude certain files. Content patterns are specified as part of the Files parameter or in lines of file specified using the --file-list command option. Use a colon (:) to separate the deployment manifest file pattern from the content patterns:
Syntax: FilePattern:ContentPattern1:ContentPattern2:...
Pattern Rules:
:*.dll:*.exe).! to exclude files (e.g., :!*.pdb).*, ?, **) are supported.Common Use Cases:
MyApp.application:*.dll:*.exe.MyApp.application:!*.pdb:!*.xml.MyAddin.vsto:*.dll:!Microsoft.Office.*.dll:!Office.dll.**/*.application:*.dll:!**/test/**.For detailed information about ClickOnce/VSTO structure and how signing works, see ClickOnce and VSTO Signing.