Discoverer: Automatic Protocol Reverse Engineering from Network Traces
By Weidong Cui, Jayanthkumar Kannan, Helen J. Wang. USENIX Security Symposium, 2007
392 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/0fd2467de521b52805eea902edc9587c87818276
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Adam Kiezun
- Paolo Milani Comparetti
- Tielei Wang
- Christopher Krügel
- Guofei Gu
- Engin Kirda
- Tao Wei
- Michael Y. Levin
Citations in the corpus
- A Survey of Payload-Based Traffic Classification Approaches (2014, background): “Another approach for automatic protocol reverse engineering was proposed in [45].”
- Prospex: Protocol Specification Extraction (2009, background): “A number of approaches [11]–[14] have been presented that use network traffic as input.”
- TaintScope: A Checksum-Aware Directed Fuzzing Tool for Automatic Software Vulnerability Detection (2010, methodology): “Many protocol reverser engineering tools (such as Prospex [31], Tupin [34], AutoFormat [47], Polyglot [26], Discoverer [33], FFE/x86 [44]) can be used to guide fuzzing tests.”
- Navigating the Data Lake with DATAMARAN: Automatically Extracting Structure from Log Datasets (2017, background): “, network protocols, or natural language corpora [7, 14, 17, 53], crucially rely”
- Grammar-based whitebox fuzzing (2008, background): “Other grammars, especially for network protocols, are simplified representatio ns of valid inputs, and do not require the full power of contextsensitivity [28, 4, 9].”