Re: tclkit signing

On 31/05/07, [email protected] <[email protected]> wrote:
> It seems codesigning tclkit based applications, as explained here:
>
> http://www.matthew-jones.com/articles/codesigning.html
>
> corrupt the tclkits, raising an "unable to find setup.tcl" error.
> This
> happens both with signcode and signtool, as if no vfs payload was
> present. The  vfs
> payload does not disappear, but somehow it is getting corrupted? In
> theory the codesigning should not affect it
>
> anybody has any ideas on how to work around this problem?

I know its been a while but I happened to get around to trying out
code signing recently and tested it out on a starpack. Signing a
starpack does indeed appear to damage the file so that the vfs cannot
be mounted. However you can use the mksplit subcommand in the sdx
utility to split the starpack into an executable and a vfs section.
You can then process the binary portion and glue them back together.
In my case I also wanted the icon to be modified so I started with a
plain, non-upxed tclkit binary
  sdx wrap tkchat.exe -runtime tclkit-gui.exe
  sdx mksplit tkchat.exe
  upx -9 tkchat.head
  signtool sign /f signing.p12 tkchat.head
  copy /b tkchat.head + tkchat.tail tkchat.exe
Now I have a working, compressed, signed starpack.

Pat Thoyts