fuzzowski
fuzzowski copied to clipboard
nccgroup
the Network Protocol Fuzzer that we will want to use.
Hello, I encountered a TypeError when running a script that involves the ctypes library in Python. Below, I have detailed the issue and my proposed solution. ### Issue Description: When...
Resolve TypeError by removing ASCII encoding from ctypes.WinDLL call. This request solves #32.
Fuzzowski send just over 100 requests to the remote server before exiting abruptly with a error "ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2396)" I can get around the issue...
Variable names with spaces caused crash when disabling a request after reaching the crash threshold with: ``` FuzzowskiRuntimeError(f'Invalid path name: {path_name}') fuzzowski.exception.FuzzowskiRuntimeError: Invalid path name: read_holding_registers.start address ```
Hi NCC Group Team Its really nice project you are working on. I have see in post by NCC group about NGAP Protocol fuzzing and you have discovered some nice...
Solution from https://github.com/emcconville/wand/issues/409 Fixed version works on termux and in some other places, where original resulted in an error
I see there is telnet connection in Fuzzowski class, but the tool's --protocol parameter doesn't support telnet yet, so if I want to test telnet, it wouldn't create TelnetConnection.
When setting a block with an encoder (eg: s_block('myblock', encoder=base64.b64encode), it is not correctly used when printing the packets, writing p0cs, or when sending the "original packet" (when using the...
Add to the argparser options the possibility of setting arbitrary variable names, so they can be used to add options to fuzzers, etc.
Add support for L2 connections and protocols, in both the session and main program