a.guelle
Posts: 97
Joined: Tue May 19, 2015 2:23 pm

[solved] Signing Tool Custom path is modified based on the running user

Wed Sep 09, 2020 10:26 am

Hi AI-Team,

seems as if your users are the QA for new versions again...

The custom path for the signing tool in 17.4.1 is not static. It changes depending on the logged on user...
Attached you can see two pictures.

On my development machine I set the path to:
C:\Bamboo\CodeSigning\signtool.exe

As soon this is transfered to the build agent, it chenges to:

C:\Bamboo\Bamboo\CodeSigning\signtool.exe

So somehow the running Windows user is added to the path.

Best regards,

Angelo
Attachments
Build-Agent.png
Build-Agent.png (4.54KiB)Viewed 5199 times
Development.png
Development.png (6.54KiB)Viewed 5199 times
Last edited by a.guelle on Thu Oct 08, 2020 10:08 am, edited 1 time in total.

Catalin
Posts: 6537
Joined: Wed Jun 13, 2018 7:49 am

Re: Signing Tool Custom path is modified based on the running user

Wed Sep 09, 2020 2:08 pm

Hello Angelo,

First of all, please accept my apologies for the encountered inconvenience.

Our QA team tests every new feature thoroughly, but unfortunately not even they can cover all the possible cases.

I have tried reproducing this issue, but I was not able to do so. Here are the steps that I took:

- create, on a virtual machine, a new project. In this project, point to:

Code: Select all

C:\Test\CodeSigning\signtool.exe
- saved the project

- copied the project from the VM to my machine

- opened the project and checked the "Digital Signature" page. The project still pointed to the same path as I gave on the VM.

I have made sure that the two users (the one from my VM and the one from my main machine) are different.

Am I missing a step here? If so, could you please let me know what else I should do in order to reproduce this?

Looking forward to hearing from you!

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Catalin
Posts: 6537
Joined: Wed Jun 13, 2018 7:49 am

Re: Signing Tool Custom path is modified based on the running user

Wed Sep 09, 2020 2:33 pm

Hello Angelo,

I have done some further investigations and it looks like the path is indeed relative to the project.

Could you please proceed as it follows:

- open the .AIP file in a text editor (e.g. Notepad++)

- find the following component:

Code: Select all

<COMPONENT cid="caphyon.advinst.msicomp.DigCertStoreComponent">
    <ROW TimeStampUrl="http://timestamp.digicert.com" SignerDescription="[|ProductName]" SignOptions="7" SignTool="0" UseSha256="1" CustomToolPath="..\..\..\Test\CodeSigning\signtool.exe" CustomToolCmdLine="sign /a /d &quot;&lt;signature description&gt;&quot; /du &quot;Description URL&quot; /fd SHA256 /tr &quot;http://timestamp.digicert.com&quot; /td sha256 "/>
  </COMPONENT>
and change the:

Code: Select all

CustomToolPath="..\..\..\Test\CodeSigning\signtool.exe"
to:

Code: Select all

CustomToolPath="C:\Test\CodeSigning\signtool.exe"
and let me know if that helps?

This way, the path should be static and you should no longer encounter this behavior.

Additionally, could you please let me know if that folder you are using is shared between the two machines (the dev machine and the build machine)?

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

a.guelle
Posts: 97
Joined: Tue May 19, 2015 2:23 pm

Re: Signing Tool Custom path is modified based on the running user

Thu Oct 08, 2020 10:08 am

Hi Catalin,

this works as explained.

Thank you very much.

Best regards,

Angelo

Catalin
Posts: 6537
Joined: Wed Jun 13, 2018 7:49 am

Re: [solved] Signing Tool Custom path is modified based on the running user

Thu Oct 08, 2020 4:58 pm

Hello Angelo,

Thank you for your followup on this.

I am glad everything works as expected now!

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”