Following up to Give the people what they want! #MOARCHECKS we'd like some input regarding our options for encapsulating service (protocol) fingerprinting data. By this, I mean the content that defines how we recognize that a port is listening for HTTP connections, for example. Of course, we already cover HTTP, so the use here would be adding descriptions of esoteric or proprietary protocols.
Please take a second to answer this one question survey: #MOARCHECKS: How should we represent service fingerprints? Survey