Skip to content
GitLab

RPC server · Changes

Page history
Updated RPC-server (markdown) authored by Tasos Laskos's avatar Tasos Laskos
Hide whitespace changes
Inline Side-by-side
guides/user/RPC-server.md
View page @ e7116eab
...@@ -15,12 +15,14 @@ of many scans across multiple nodes. ...@@ -15,12 +15,14 @@ of many scans across multiple nodes.
_If you are interested in providing webappsec scanning services you can write _If you are interested in providing webappsec scanning services you can write
your own client using the [[RPC API]]._ your own client using the [[RPC API]]._
## Version 0.4.2 ## Version 0.4.3
* [Simple setup](#simple) * [Simple setup](#simple)
* [High Performance Grid setup](#grid) * [Grid setup](#grid)
* [Example](#grid-example) * [Load balancing](#grig-load-balancing)
* [Mock example](#grid-mock-example) * [Line Aggregation](#grig-line-aggregation)
* [Example](#grid-line-aggregation-example)
* [Mock example](#grid-line-aggregation-mock-example)
* [Security considerations](#security) * [Security considerations](#security)
* [Help output](#help) * [Help output](#help)
...@@ -30,7 +32,11 @@ Starting a Dispatcher can be as simple as running: `arachni_rpcd` ...@@ -30,7 +32,11 @@ Starting a Dispatcher can be as simple as running: `arachni_rpcd`
This will bind on `localhost:7331` by default. This will bind on `localhost:7331` by default.
### <a id="grid" href="#grid">High Performance Grid setup</a> ### <a id="grid" href="#grid">Grid setup</a>
#### <a id="grid-load-balancing" href="#grid-load-balancing">Load balancing</a>
#### <a id="grid-line-aggregation" href="#grid-line-aggregation">Line aggregation</a>
In order to connect the Dispatchers into a grid you'll need to: In order to connect the Dispatchers into a grid you'll need to:
...@@ -43,7 +49,7 @@ In order to connect the Dispatchers into a grid you'll need to: ...@@ -43,7 +49,7 @@ In order to connect the Dispatchers into a grid you'll need to:
After that, they will build and maintain their network themselves. After that, they will build and maintain their network themselves.
#### <a id="grid-example" href="#grid-example">Example</a> ##### <a id="grid-line-aggregation-example" href="#grid-line-aggregation-example">Example</a>
Running the first Dispatcher: Running the first Dispatcher:
...@@ -58,7 +64,7 @@ Lather, rinse, repeat: ...@@ -58,7 +64,7 @@ Lather, rinse, repeat:
arachni_rpcd --pipe-id="Pipe 3" --nickname="My third Dispatcher" --address=192.168.0.3 --neighbour=192.168.0.2:7331 arachni_rpcd --pipe-id="Pipe 3" --nickname="My third Dispatcher" --address=192.168.0.3 --neighbour=192.168.0.2:7331
arachni_rpcd --pipe-id="Pipe 4" --nickname="My forth Dispatcher" --address=192.168.0.4 --neighbour=192.168.0.3:7331 arachni_rpcd --pipe-id="Pipe 4" --nickname="My forth Dispatcher" --address=192.168.0.4 --neighbour=192.168.0.3:7331
#### <a id="grid-mock-example" href="#grid-mock-example">Mock example</a> ##### <a id="grid-line-aggregation-mock-example" href="#grid-line-aggregation-mock-example">Mock example</a>
The above setup assumes that each Dispatcher is on a machine with independent bandwidth lines The above setup assumes that each Dispatcher is on a machine with independent bandwidth lines
(to the target website at least). If you want to, out of curiosity, start a few Dispatchers on (to the target website at least). If you want to, out of curiosity, start a few Dispatchers on
......