vbatts
/
fuzz-walker
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity
An extendable filesystem walker to poke at a host.
9 Commits 1 Branch 0 Tags 938 KiB
Go 89.4%
Makefile 5.4%
Shell 5.2%
Go to file
Vincent Batts e1167b07b3
add a container build script 
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
 		2018-06-06 13:00:10 -04:00
vendor *: proper cli and vendoring 2018-06-05 16:53:08 -04:00
walker default to compile in, but also allow plugins 2018-06-06 12:29:33 -04:00
.gitignore switching to plugins 2018-06-06 10:43:43 -04:00
LICENSE README and LICENSE 2018-06-06 12:38:36 -04:00
Makefile default to compile in, but also allow plugins 2018-06-06 12:29:33 -04:00
README.md README and LICENSE 2018-06-06 12:38:36 -04:00
build.sh add a container build script 2018-06-06 13:00:10 -04:00
main.go default to compile in, but also allow plugins 2018-06-06 12:29:33 -04:00
vendor.conf *: proper cli and vendoring 2018-06-05 16:53:08 -04:00

README.md

fuzz-walker

A simple filesystem walker to poke around system paths and cause the system to invalidate or crash.

Building

You can easily:

go get git.thisco.de/vbatts/fuzz-walker

Additionally, you write your own walker functions as plugins. See git.thisco.de/vbatts/fuzz-walker/walker package for data structures, and https://git.thisco.de/vbatts/fuzz-walker/src/master/walker/walkers/readFuzz/plugin.go as an example. This way you need no edit and recompile fuzz-walker itself over and over.

running

I reckon you could run this on your host, but it's intended to push the bounds of what's allowed inside a container.

fuzz-walker

LICENSE

See LICENSE