Azure key vault signing fall in IDE

[bill.me]

Here is the log:

[ Development ]
Building package:
C:\_Published\Manager\ManagerInstall.exe
Prepare build
Detecting MSI incompatible resources
Preparing files
Creating CAB file(s)
Signing CAB file(s)
Preparing binaries
Creating MSI database
Writing Summary Information
Signing MSI
Could not read server response.
Error details


And error details:

Could not read server response.

Advanced Installer 21.3.1 build 69aaef70
*** Stack Trace (x86) ***

[0x757d9392] RaiseException()
[0x509a7e86] CxxThrowException()
[0x007cae48] -----
[0x73d9c4ec] HttpQueryInfoW()
[0x00150000] MODULE_BASE_ADDRESS

[Liviu]

Hello,

I replied on the other thread debating this issue.

You can check my reply here.

To assist us in conducting a thorough investigation of this issue, can you please send us the .AIP (project file) via email to support at advancedinstaller dot com, without the TenantID and APPID?

Best regards,
Liviu

[maxschaf]

We have something similar; our builds suddenly fail since yesterday, we are not aware of any change made.

Exit code of C:\Program Files (x86)\Caphyon\Advanced Installer 20.2.1\bin\x86\AdvancedInstaller.com was -536805276

any idea what this means? signing issue, key vault shows authentication errors... but the secret etc. are fine, they work with AzureSignTool, etc.

[maxschaf]

Could not read server response.

Build finished because an error was encountered.


I think they turn off old tls versions...

[maxschaf]

The network requests within AI to key vault fail most (!) of the time, AI is not resilient to network error. So we retry building AI project now for up to 15 times and this helps as a workaround.
AzureSignTool is more resilient and works. Please improve AI!

[Daniel]

Hi,

Thank you for your feedback on this! We are currently working as we speak to some improvement that we hope will avoid such issues.

In the meantime, as a workaround solution you can try indeed to use the "azuresigntool.exe" tool to sign your setup project. This tool can be install using the following dotnet command:

Code: Select all

dotnet tool install --global AzureSignTool --version 4.0.1

Then, all you need to configure in "Digital Signatures" page of your setup project is a custom command line like this:

Code: Select all

sign -du "https:\\<YourDescriptionURL>" -fd sha256 -kvi "<AppID>" -kvt "<TenantID>" -kvu "https://<VaultName>.vault.azure.net" -kvs "<AppSecret>" -kvc "<certificateName>" -tr "http://timestamp.digicert.com" -td sha256 -v

screenshot.jpg (75 KiB) Viewed 14066 times

Hope this helps.

As soon as we have a version of Advanced Installer with improvements in this regard we will update this forum thread too.

All the best,
Daniel

[maxschaf]

Hi,

thanks for your answer. we tried AzureSignTool v3 in AI this morning and we had the same issue some times; we decided to just restart the AI up to 15 times in our pipelines and this works as a workaround for us.

We are looking forward to your AI improvement and we will upgrade AI then. It looks like we are good with our retries in the mean time.

Best.

[Daniel]

Hi,

Can you please download and use the following debug version of Advanced Installer 21.5? And let us know if this makes any difference?

This includes some improvements we hope will fix this issue.

All the best,
Daniel