You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to sign an exe or msi file I see a warning "The certificate has expired"
Signing Chem4Word-Setup.exe
warn: Sign.Core.ICertificateVerifier[0]
The certificate is expired.
info: Sign.Core.ISigner[0]
Submitting C:\Temp\Chem4Word-Setup.exe for signing.
info: Sign.Core.ISigner[0]
SignAsync called for C:\Temp\Chem4Word-Setup.exe. Using C:\Users\Mike.Williams\AppData\Local\Temp\eqmfcnwy.p22\b1nkgwx1.exe locally.
info: Sign.Core.ISignatureProvider[0]
Signing SignTool job with 1 files.
info: Sign.Core.ISignatureProvider[0]
Signing C:\Users\Mike.Williams\AppData\Local\Temp\eqmfcnwy.p22\b1nkgwx1.exe.
fail: Sign.Core.ISignatureProvider[0]
Signing failed with error -2146762486.
info: Sign.Core.ISignatureProvider[0]
Performing attempt #2 of 3 attempts after 5 s.
info: Sign.Core.ISignatureProvider[0]
Signing C:\Users\Mike.Williams\AppData\Local\Temp\eqmfcnwy.p22\b1nkgwx1.exe.
fail: Sign.Core.ISignatureProvider[0]
Signing failed with error -2146762486.
info: Sign.Core.ISignatureProvider[0]
Performing attempt #3 of 3 attempts after 11.1803398 s.
Sign was setup for us approx a year ago so it is concievable that it is the certificate stored in our Azure Key Valut that has expired and needs renewing
-kvt, --azure-key-vault-tenant-id <azure-key-vault-tenant-id> Tenant ID to authenticate to Azure Key Vault.
-kvi, --azure-key-vault-client-id <azure-key-vault-client-id> Client ID to authenticate to Azure Key Vault.
Describe the bug
When trying to sign an exe or msi file I see a warning "The certificate has expired"
Sign was setup for us approx a year ago so it is concievable that it is the certificate stored in our Azure Key Valut that has expired and needs renewing
This is the command line I am using
Please help
I can supply the values for by PM
To whever is assigned to this issue
Additional context
The text was updated successfully, but these errors were encountered: