Post
You need to pin both the publisher ID and the Microsoft CAs. Only Microsoft CAs are supposed to use this special publisher ID encoded in the EKU OIDs, there's no reason to see it with third-party CAs not used in Azure Artifact Signing
0 reposts0 likes
I wrote Get-AzTrustedSigningEkuOid github.com/jborean93/Po... to extract this from a cert. It probably should be updated to also compare something up the chain is the same to convey that it came from the same source but I just don't know. In PKI not knowing is dangerous when doing stuff like this :)
github.comPowerShell-OpenAuthenticode/docs/en-US/about_AuthenticodeAzureTrustedSigning.md at main · jborean93/PowerShell-OpenAuthenticodeCross platform PowerShell implementation of Authenticode signing and verification - jborean93/PowerShell-OpenAuthenticode
I added support for pinned publisher ID validation with the Azure Artifact Signing CAs in psign today and generated some docs here: github.com/Devolutions/...
github.compsign/docs/artifact-signing-validation.md at master · Devolutions/psignPortable code signing tool. Contribute to Devolutions/psign development by creating an account on GitHub.