Skip to content

Commit d3ce60f

Browse files
authored
Update running tests with the new flags (#1476)
1 parent b8228e9 commit d3ce60f

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

Diff for: src/tests/running.md

+9-3
Original file line numberDiff line numberDiff line change
@@ -245,14 +245,20 @@ The binary will be created at
245245
`./build/$HOST_ARCH/stage2-tools/$TARGET_ARCH/release/remote-test-server`. Copy
246246
this over to the remote machine.
247247

248-
On the remote machine, run the `remote-test-server` with the `remote` argument
249-
(and optionally `-v` for verbose output). Output should look like this:
248+
On the remote machine, run the `remote-test-server` with the `--bind
249+
0.0.0.0:12345` flag (and optionally `-v` for verbose output). Output should
250+
look like this:
250251
```sh
251-
$ ./remote-test-server -v remote
252+
$ ./remote-test-server -v --bind 0.0.0.0:12345
252253
starting test server
253254
listening on 0.0.0.0:12345!
254255
```
255256

257+
Note that binding the server to 0.0.0.0 will allow all hosts able to reach your
258+
machine to execute arbitrary code on your machine. We strongly recommend either
259+
setting up a firewall to block external access to port 12345, or to use a more
260+
restrictive IP address when binding.
261+
256262
You can test if the `remote-test-server` is working by connecting to it and
257263
sending `ping\n`. It should reply `pong`:
258264
```sh

0 commit comments

Comments
 (0)