MIC?
message integrity check - like MD5 or SHA-1.
(and you have to include the MIC for the whole message along with
every fragment. however you can also use the MIC as the message
identifier, which might be kind of handy)
For that matter, only a fool would
download binaries from USENET without doing all kinds of testing.
or for that matter, from the web, or ftp, or anywhere else.
but there's such a thing as making it too easy to do harm.
it's not terribly difficult to steal a tcp connection if
you have access to the signal path. but when sending fragmented
files over usenet, everybody has access to the signal path.
I don't know of any good way to test binaries for possible malicious
activity - there are too many ways to do harm.
Keith