VERY Minor problem

[NewsArchive]

Friedrich,

VERY minor issue but thought I would pass it on. I have my scripts set
to NOT permanently code sign them. I am also using the older method to
code sign the files if that matters and the latest release of SB.

If a coding signing of one of the files fails, when I go back and try
again, that one file indicates that it is already code signed. Any
other files that where signed prior to the failure will sign as I
would expect without any warnings.

So it appears that when the signing fails on a file, that one and only
one file does not seem to revert back to the original but keeps the
modified one.

Again, not a big deal and this has been happening for a long while.
Just thought that I would pass it on.

Barton Whisler


Barton Whisler
Prosoft Inc.
Tampa, Florida

[NewsArchive]

Hi Barton,

Thanks for the report.

Hmmm, nothing changed in the code-signing feature for years (to be honest, I
don't remember an "older" method to code-sign files -- the "Permanent"
option was always there).

But I'll check the source code to see if there is any potential issue with
the "rollback" feature.

Thanks,
Friedrich

[NewsArchive]

Barton,

> So it appears that when the signing fails on a file, that one and
> only one file does not seem to revert back to the original but
> keeps the modified one.

Do you have any idea why it fails to code-sign? Perhaps the virus scanner
"locks" the file during the code-signing process (that's why Authenticode
signing fails) and does not release the lock quickly enough. After that,
the compiler is unable to "rollback" to the original version because that
file is still locked by the protection software.

I'll see if we can add some code to detect such a rollback issue caused by
"locked" file(s).

Thanks again for your report.

Friedrich

[NewsArchive]

Friedrich,

The older method I was referring to is the code signing "Signcode.exe"
tool as opposed to the newer tool.

As far as why, I am not sure. It only happens maybe one in a hundred
times or less with no particular pattern. If also occurs in different
locations of the files being code signed. Sometime near the first one
signs and sometime farther down the list of files.

The current installation is on Microsoft Window 2003 Server R2 running
with AVG Server version anti-virus. But have seen also on a local
Window 7 & 8 installation running Microsoft Security Essentials. By
long, this has occurred more than three years and probably more than
that.

Finally, it is NOT that big of a deal as the end result is still fine.
So if not something obvious, don't worry about it. Just mentioned it
in case it was an easy fix.

Barton

Barton Whisler
Prosoft Inc.
Tampa, Florida

[NewsArchive]

Barton,

Aha, okay. Thanks for the information!

I think "something" temporarily locked the file and as a result, the
compiler failed to rollback to the original. We'll try to add some code so
the compiler can detect this scenario.

Thanks again!!!

Friedrich