v22 expired!

[vefatica]

I just upgraded to build 32. It came up expired. When I pressed "Register" everything disappeared. So I uninstalled, downloaded the distribution and re-installed. The same thing happened ... expired ... "Register" made it disappear.

I did a little better with TCMD ... unregistered ... press "Register" ... no registration dialog but TCMD stayed open ... options ... register ... registration successful ... but the next time I start it, expired!

 

[rconn]

That means Windows couldn't verify the code auth signature on the executable (TCC.EXE or TCMD.EXE). Did you do anything to modify the files?

 

[vefatica]

That means Windows couldn't verify the code auth signature on the executable (TCC.EXE or TCMD.EXE). Did you do anything to modify the files?

Yes, I've been patching 4 bytes of TCC.EXE since v21 to eliminate its polling its own window twice a second.. What was that polling for? I have forgotten.

Is this something new? I notice that I can edit the binary in other ways and it still works. For example, I can use EDITBIN to make a subsystem:windows version of it.

 

[rconn]

Yes, I've been patching 4 bytes of TCC.EXE since v21 to eliminate its polling its own window twice a second.. What was that polling for? I have forgotten.

Then the behavior on your system is WAD.

[/QUOTE]Is this something new? I notice that I can edit the binary in other ways and it still works. For example, I can use EDITBIN to make a subsystem:windows version of it.[/QUOTE]

It's Windows that is validating the EXE. The code signature probably doesn't include everything in the header.

 

[vefatica]

Is this something new? I've patched every build of v21 and v22 since August 2017.

 

[rconn]

Is this something new? I've patched every build of v21 and v22 since August 2017.

That has never been supported. It isn't anything new in TCC -- Windows should never have allowed you to do that to a signed executable.

 

[vefatica]

That has never been supported. It isn't anything new in TCC -- Windows should never have allowed you to do that to a signed executable.

As I said, it had worked many times, notably with every build of v22 until this one. This time, the patch is at exactly the same place in the file as in the previous build. In fact, I can uninstall build 32, re-install build 31, patch it, and it works fine!

 

[rconn]

The build 32 behavior is correct.

 

[vefatica]

The build 32 behavior is correct.

Is the new behavior also supposed to screw up running TCC in WinDbg? It does.

 

[rconn]

Is the new behavior also supposed to screw up running TCC in WinDbg? It does.

TCC and TCMD have always had code to prevent them from being run in a debugger.