exit-signal vs openssh

[der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>]

Is it my imagination, or does OpenSSH 3.4 generate exit-signal channel
requests that do not conform to connect-18?  (Presumably it was written
to an older draft?)

I'm seeing packets with payload (after the want-reply boolean) of 
	00 00 00 01 00 00 00 00 00 00 00 00 00
which makes sense only if I read the signal as uint32 instead of
string.  Source to openssh 3.6.1 implies that it does send a string,
though as I don't have binaries I can't easily check.  It doesn't
include a compatability quirk for this, but as it appears to completely
ignore exit-signal messages it may well not care.

Is there a recommended heuristic for detecting this?  Or would I be
best off just not even trying to parse exit-signal messages?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse%rodents.montreal.qc.ca@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B