*sigh*
Okay, so the signature files are created by taking an MD5 hash of the file and using an 1024-bit private RSA key. Yes, this is what we thought, but now I can be certain of it.
However, the !$!@$ thing then applies some bizzarro bit-scrambling function to it; this may be what inflates the sizeof the sig files, I don't know.
Google wasn't much help ... it involves the constants 0, 0x40100401, 0x80200802, 0xC0300C03 and 0x3FCFF3FC. Oh. and there's some sort of debug function (that's never called) in phatd that uses these numbers and spits out the letters "Z", "O", "P", "M" along with some numbers.
I need to go to sleep now, it's someone else's turn.
-b
PS - Oh, and Para -- sorry I missed your question before. If you yank any of the keys out of any of the binaries, the first 16 bits of the key reads 0x0400 -- for 1024 bits.
-b