test - invalid inputs

[jmccormick2001]

[gregscds]

Here are a few starter examples for invalid inputs that should be caught, or at least result in a clean shutdown rather than a crash:

• Zero and/or negative numbers for parts of the protocol message that are normally small positive numbers.
• Zero length annotation.
• Connect via an unsupported protocol.
• Incoming packets that are too short and end in the middle of the protocol conversation. (Eventually this idea leads to complicaated fuzz testing, but a couple of hard coded short malformed messages would be fine to get started)
• Passing Unicode or similar non-ASCII text, to the extent that is supported in the protocol itself.

[jmccormick2001]

thanks Greg!