Describe the bug
This is essentially a duplicate of #852; I was asked by @TacoTechSharma to raise a separate issue to elaborate on the urgency.
I just switched Git for Windows to code-signing with Azure Artifact Signing. As Git for Windows offers support for Windows/ARM64, it was highly crucial to code-sign also the Windows/ARM64 bits. Currently, this is done via a crude work-around because dotnet/sign simply doesn't work as advertised on ARM64.
Repro steps
Use the recommended signtool.exe invocation on Windows/ARM64.
Expected behavior
Correctly code-signs an executable on Windows/ARM64, just like it does on Windows/x64.
Actual behavior
Fails. See #852 for details.
Additional context
sign --version: any.dotnet --info: any.
We currently use a really ugly work-around, which is not ideal.
Describe the bug
This is essentially a duplicate of #852; I was asked by @TacoTechSharma to raise a separate issue to elaborate on the urgency.
I just switched Git for Windows to code-signing with Azure Artifact Signing. As Git for Windows offers support for Windows/ARM64, it was highly crucial to code-sign also the Windows/ARM64 bits. Currently, this is done via a crude work-around because
dotnet/signsimply doesn't work as advertised on ARM64.Repro steps
Use the recommended
signtool.exeinvocation on Windows/ARM64.Expected behavior
Correctly code-signs an executable on Windows/ARM64, just like it does on Windows/x64.
Actual behavior
Fails. See #852 for details.
Additional context
sign --version: any.dotnet --info: any.We currently use a really ugly work-around, which is not ideal.