Code signing changes filename case

[NewsArchive]

Hi Friedrich,

I've noticed something strange when I code sign the BuildAutomator.exe
When I code sign it, it changes to buildautomator.exe

I had noticed before that the name had changed, but thought it was
just me<g> Apparently it's the code signing;)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> I've noticed something strange when I code sign the BuildAutomator.exe
> When I code sign it, it changes to buildautomator.exe
>
> I had noticed before that the name had changed, but thought it was
> just me<g> Apparently it's the code signing;)

Unfortunately, I can't reproduce it here. See attached screenshots. It
never changes from BuildAutomator.exe to buildautomator.exe. I even tried
buildautomator.exe (all lower-case) as "File Name", same result.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

>Unfortunately, I can't reproduce it here. See attached screenshots. It
>never changes from BuildAutomator.exe to buildautomator.exe. I even tried
>buildautomator.exe (all lower-case) as "File Name", same result.

I'll take a closer look. I know it happens during the install compile
process but I could not see anything in the script that did anything
to the exe file except the code signing. I'll let you know what I can
find.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

> I'll take a closer look. I know it happens during the install compile
> process but I could not see anything in the script that did anything
> to the exe file except the code signing. I'll let you know what I can
> find.

Thank you, Arnór!

Friedrich

[NewsArchive]

Arnor -

When BuildAutomator.exe gets signed, does it get signed to a copy, or
does it get signed where it is? If it gets signed to a copy, maybe the
problem is that the existing file already is named
"buildautomator.exe".

If this is the case, delete the existing "buildautomator.exe"

Just a thought.

Jeff Slarve
CSA

[NewsArchive]

Hi Jeff,

> When BuildAutomator.exe gets signed, does it get signed to a copy, or
> does it get signed where it is? If it gets signed to a copy, maybe the
> problem is that the existing file already is named
> "buildautomator.exe".
>
> If this is the case, delete the existing "buildautomator.exe"
>
> Just a thought.

And what a good thought this is. I think you are right. It seems to be
caused by a copy process when the "Permanent" code-sign option is not
enabled and the compiler restores the original file (overwrites the existing
file via the CopyFile API). I can reproduce this now.

Item in review.

Thanks again,
Friedrich

[NewsArchive]

Hi Jeff,

>When BuildAutomator.exe gets signed, does it get signed to a copy, or
>does it get signed where it is? If it gets signed to a copy, maybe the
>problem is that the existing file already is named
>"buildautomator.exe".
>
>If this is the case, delete the existing "buildautomator.exe"

It is signed where it is, i.e.:

C:\Products\BuildAutomator\Latest\Program Files\Icetips Creative\Build
Automator\BuildAutomator.exe

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

>Unfortunately, I can't reproduce it here. See attached screenshots. It
>never changes from BuildAutomator.exe to buildautomator.exe. I even tried
>buildautomator.exe (all lower-case) as "File Name", same result.

Ok. This is not caused by the code signing of the exe at all. This
happens at the very end of the compile process. If I put a #msgbox at
the end of my script, the exe is still BuildAutomator.exe. When the
compile process is done, it's changed to buildautomator.exe

Obviously not a big issue<g> Since the code signing is the only thing
that the script does to the exe, I thought this was happening because
of that. It's not.

I have been through the script to check if there is a lowercase
version of the name somewhere that might be causing this, but I can't
find it.

Would you like to take a look at this script?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Ok. This is not caused by the code signing of the exe at all. This
> happens at the very end of the compile process. If I put a #msgbox at
> the end of my script, the exe is still BuildAutomator.exe. When the
> compile process is done, it's changed to buildautomator.exe
>
> Obviously not a big issue<g> Since the code signing is the only thing
> that the script does to the exe, I thought this was happening because
> of that. It's not.
>
> I have been through the script to check if there is a lowercase
> version of the name somewhere that might be causing this, but I can't
> find it.
>
> Would you like to take a look at this script?

I think Jeff hit the nail on the head. It's caused by a copy process. I
assume you have the "Permanent" option in the code-sign directive not
enabled, right?

Friedrich

[NewsArchive]

Hi Friedrich,

>I think Jeff hit the nail on the head. It's caused by a copy process. I
>assume you have the "Permanent" option in the code-sign directive not
>enabled, right?

Correct. Since this is always working on a version copy I don't care
if it's permanent or not as the file being code signed is always not
code signed and never used for anything except the install.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Correct. Since this is always working on a version copy I don't care
> if it's permanent or not as the file being code signed is always not
> code signed and never used for anything except the install.

If "Permanent" is not enabled then the compiler restores the original (not
code-signed) file after the compilation process. This issue is definitely
caused by the CopyFile process. It's on the "Items to review" list.

Friedrich

[NewsArchive]

Hi Friedrich,

>If "Permanent" is not enabled then the compiler restores the original (not
>code-signed) file after the compilation process. This issue is definitely
>caused by the CopyFile process. It's on the "Items to review" list.

Cool:) I have checked the Permanent as it doesn't make much
difference for me one way or the other:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

> Cool:) I have checked the Permanent as it doesn't make much
> difference for me one way or the other:)

Hmm, if the "Permanent" option does not make a difference for you then it's
not caused by this. I can reproduce the problem if I do not set the
"Permanent" checkbox. If the "Permanent" checkbox is marked then it does
not change the case of the filename here. Strange.

Friedrich

[NewsArchive]

Hi Friedrich,

>> Cool:) I have checked the Permanent as it doesn't make much
>> difference for me one way or the other:)
>
>Hmm, if the "Permanent" option does not make a difference for you then it's
>not caused by this. I can reproduce the problem if I do not set the
>"Permanent" checkbox. If the "Permanent" checkbox is marked then it does
>not change the case of the filename here. Strange.

No you misunderstand. It FIXES the naming problem:) What I mean is
that the Permanent being checked doesn't make any difference for my
install<g> I don't care if it's permanent or not since I never use
the exe once it's packed in the install:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

" No you misunderstand. It FIXES the naming problem:) What I mean is
> that the Permanent being checked doesn't make any difference for my
> install<g> I don't care if it's permanent or not since I never use
> the exe once it's packed in the install:)

Aha, okay :)

Friedrich

[NewsArchive]

Hi Arnór,

Fixed in both "#code-sign application..." and "#embed Vista manifest..."

Thank you for bringing this to my attention.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner