Skip to content

Do not use hash verification to install the latest version of WinDbg #1331

Closed
@Ana06

Description

@Ana06

Details

At the moment we use hash verification to install WinDbg. Because of the unusual version format (1-2402-24001) our automation is not able to update the URL/hash. Consequently the version/hash have to be updated manually, causing that we now don't install the latest WinDbg version.

We can use an URL without a version for tools that are signed using VM-Assert-Signature. It uses signtool.exe to verify the tool instead of the hash. We use it for example to install sysinternals.

But it seems not to be possible to verifying https://aka.ms/windbg/download with signtool.exe:

> &"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\signtool.exe" verify /pa  .\windbg.appinstaller
File: .\windbg.appinstaller
Index  Algorithm  Timestamp
========================================
SignTool Error: This file format cannot be verified because it is not
        recognized.

Number of errors: 1

We are using Add-AppxPackage to install the package and I see -AllowUnsigned as a flag. So maybe this means we could skip the verification at all, but I am not sure. 😕

Does anyone have more information or ideas about how we can install WinDbg without using hash verification (using other type of versification) to ensure we have the latest version installed? @vm-packages @TimMisiak @naacbin @binjo @stevemk14ebr

Metadata

Metadata

Assignees

Labels

😕 needs infoFurther information is needed🌀 FLARE-VMA package or feature to be used by FLARE-VM💎 enhancementIt is working, but it could be better❔ discussionFurther discussion is needed

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions