Skip to content
This repository was archived by the owner on Mar 4, 2025. It is now read-only.

Commit 8de5222

Browse files
committed
Update readme
1 parent 09b53cb commit 8de5222

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
21
**NOTE** Since this framework performs a lot of system-level configuration changes to operate
32
it is highly recommended to create an environment for this inside a VM.
43

@@ -77,4 +76,5 @@ You can use the following instructions to do so:
7776
- Run the selenium backend: `java -jar selenium-server-standalone-3.4.0.jar`
7877
- 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
7978
- 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
8080
- 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

Comments
 (0)