Pet.exe not signed properly

[Deurslingeraar]

We are currently implementing Application Control for Business and some of our users use the Python vscode extension.
Now we want to whitelist pet.exe but to our surprise it was signed without ProductName see screenshot :

For now this is a blocking issue since we cannot do proper whitelisting without allowing the full 2011 certificate which means that everything can be installed that has the 2011 MS certificate.
Path of this file is : C:\Users\MyUsername.vscode\extensions\ms-python.python-2025.18.0-win32-x64\python-env-tools\bin\Pet.exe

Can you please sign this .exe properly with ProductName in your future deployments.

[eleanorjboyd]

@karthiknadig or @DonJayamanne do one of you know if this change is required in this repo or in the PET repo?

[karthiknadig]

This should go in the PET repo. Raymond might be able to help with this one.

[eleanorjboyd]

@rzhao271 looping you in i you have any idea on how to help here

[Deurslingeraar]

@rzhao271 Any update on this we did a file hash whitelisting but after an update we need to create a new rule since the file hash changed.

[rzhao271]

I am currently working on housekeeping and plan to look more into the issue in January.
I did look at the pipeline templates, though, and noticed that we already tell the sign tool which binary to sign, but that the sign tool does not seem to pick up the product name or OpusName parameter.

Could you take a screenshot of how the Custom Rules window looks when you inspect VS Code's Code.exe?