How ernw/dizzfiles works
Main Components
a. Protocol Modules Layer
• Protocols into related categories:
• Network Protocols (ARP, CDP, LLDP, VXLAN)
• Internet Protocols (IPv6, ICMP, DHCP)
• Application Protocols (HTTP, SIP)
• Storage Protocols (NFSv3, NFSv4)
• Mobile/Telecom Protocols (GTP_v1, GTP_v2, GSM_MAP)
• Device Protocols (USB)
• Security Protocols (SSL)
b. Fuzzing Engine Interface Layer
• How these scripts interface with the Dizzy fuzzing toolkit
• .dizz file format as the connection point
c. Test Execution Layer
• Action files (.act)
• Test case generation flow
┌─────────────────────────────────────────┐
• Dizzy Fuzzing Engine │
• ┘
• ↑
┌─────────────────────────────────────────┐
• Protocol Fuzzing Scripts │
• ┬─────────┬─────────┬──────────┤
• Network │Internet │ App │ Storage │
• Protocol │Protocol │Protocol │Protocol │
• Scripts │Scripts │Scripts │Scripts │
• ┴─────────┴─────────┴──────────┘
Important Elements to Highlight
a. Protocol Implementation Structure
• How complex protocols (like NFSv4) have multiple components:
• Core operation files
• Action scripts
• Supporting modules
b. Test Flow Representation
• How test cases are generated
• Relationship between .dizz and .act files
Specific Details
a. File Type Relationships:
• .dizz files → Test Definitions
• .act files → Test Actions
• .py files → Supporting Logic
b. Protocol-Specific Components:
• Related protocol operations
• Dependencies between operations
The interface with the Dizzy fuzzing engine
Remember to maintain a balance between showing the overall architecture while providing enough detail to understand the relationship between different components and their role in the fuzzing process.