You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 4, 2025. It is now read-only.
Copy file name to clipboardexpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,3 @@
1
-
2
1
**NOTE** Since this framework performs a lot of system-level configuration changes to operate
3
2
it is highly recommended to create an environment for this inside a VM.
4
3
@@ -77,4 +76,5 @@ You can use the following instructions to do so:
77
76
- Run the selenium backend: `java -jar selenium-server-standalone-3.4.0.jar`
78
77
- Run the proxy server using the IP address where the firmware is exposing the web API. You can find this looking at the `run.sh` script that is generated for the emulated firmware
79
78
- The proxy server can be run as `mitmdump -R http://192.168.10.1 -s proxylogger.py`
79
+
- If you know the credentials to authenticate with the firmware, put username in first line and password in the second line (with `_` for blank) in `data/credentials.txt` to bootstrap the fuzzing process
80
80
- With these components up, the fuzzer can be fired up. An example invocation is provided that tests CI: `python fuzzer.py -d ~/location/of/emulated/firmware/ -u http://0.0.0.0:8080 -v 1 -a 1
0 commit comments