Code signing PAR follow-up

[Daniel Caspi]

I think I've made some progress in identifying some of the causes of the
failure of PAR packed apps to code sign on Mac OSX.

One thing in particular is that the code signature extends the length of
the binary. It seems like the PAR executable has to end with "\nPAR\n". If
I tamper with the binary in any way (e.g., add an extra character to the
end of the file), PAR displays a default "Usage" message...e.g. [ -Alib.par
] [ -Idir ] [ -Mmodule ] [ src.par ] [ program.pl ].

The code signature needs to add characters at the end of this binary in
order to be valid. Is there a way to have PAR ignore characters after this
final \nPAR\n for packed executables?

Thanks for your help all.

I think this fix + Mach-O fixes to the header sizes will allow PAR apps to
codesign, but still working on this. Will post a solution once available.

Thank you,
Dan

[Roderich Schupp]

One thing in particular is that the code signature extends the length of the
binary. It seems like the PAR executable has to end with "\nPAR\n".

Correct.

The code signature needs to add characters at the end of this binary in
order to be valid. Is there a way to have PAR ignore characters after this
final \nPAR\n for packed executables?

One might relax that to "\nPAR\n" within the last 4K of the packed executable
with little effort.

Cheers, Roderich