Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Wiki
  • Guides
  • User
  • RPC server

RPC server · Changes

Page history
Updated RPC-server (markdown) authored Aug 03, 2014 by Tasos Laskos's avatar Tasos Laskos
Hide whitespace changes
Inline Side-by-side
guides/user/RPC-server.md
View page @ 52ae8434
# RPC Server (Dispatcher) -- v0.4.6
# Dispatcher -- v1.0
Dispatchers are remote agents which provide you with scanner _Instances_ -- _Instances_
are the entities that actually perform the scans.
......@@ -128,7 +128,7 @@ Sufficient authN/authZ can be achieved by either:
The help output of the RPC server if fairly straightforward:
```
Arachni - Web Application Security Scanner Framework v0.4.6
Arachni - Web Application Security Scanner Framework v1.0
Author: Tasos "Zapotek" Laskos <[email protected]>
(With the support of the community and the Arachni Team.)
......@@ -137,60 +137,72 @@ Arachni - Web Application Security Scanner Framework v0.4.6
Documentation: http://arachni-scanner.com/wiki
Usage: arachni_rpcd [options]
Usage: ./bin/arachni_rpcd [options]
Supported options:
Generic
-h, --help Output this message.
-h
--help output this
--version Show version information.
--address=<host> specify address to bind to
(Default: localhost)
Server
--address ADDRESS Hostname or IP address to bind to.
(Default: 127.0.0.1)
--external-address=<host> specify the external address used to access this Dispatcher
(Defaults to the value of '--address'.)
--external-address ADDRESS
Hostname or IP address to advertise.
(Default: 127.0.0.1)
--port=<num> specify port to listen to
(Default: 7331)
--port NUMBER Port to listen to.
(Default: 7331)
--port-range=<beginning>-<end>
--port-range BEGINNING-END
Specify port range for the spawned RPC instances.
(Default: 1025-65535)
specify port range for the RPC instances
(Make sure to allow for a few hundred ports.)
(Default: 1025-65535)
--pool-size SIZE How many Instances to have available at any given time.
(Default: 5)
--reroute-to-logfile reroute all output to a logfile under 'logs/'
--pool-size=<num> how many server workers/processes should be available
at any given moment (Default: 5)
Output
--reroute-to-logfile Reroute all output to log-files under: /Users/zapotek/workspace/arachni/logs/
--neighbour=<URL> URL of a neighbouring Dispatcher (used to build a grid)
--verbose Show verbose output.
(Only applicable when '--reroute-to-logfile' is enabled.)
--weight=<float> weight of the Dispatcher
--debug [LEVEL 1-3] Show debugging information.
(Only applicable when '--reroute-to-logfile' is enabled.)
--pipe-id=<string> bandwidth pipe identification
--only-positives Only output positive results.
(Only applicable when '--reroute-to-logfile' is enabled.)
--nickname=<string> nickname of the Dispatcher
--debug
Grid
--neighbour URL URL of a neighbouring Dispatcher.
--weight FLOAT Weight of this node.
SSL --------------------------
--pipe-id ID Identifier for the attached bandwidth pipe.
(All SSL options will be honored by the dispatched RPC instances as well.)
(Do *not* use encrypted keys!)
--nickname NAME Nickname for this Dispatcher.
--ssl-pkey <file> location of the server SSL private key (.pem)
(Used to verify the server to the clients.)
--ssl-cert <file> location of the server SSL certificate (.pem)
(Used to verify the server to the clients.)
SSL
--ssl-ca FILE Location of the CA certificate (.pem).
--node-ssl-pkey <file> location of the client SSL private key (.pem)
(Used to verify this node to other servers.)
--server-ssl-private-key FILE
Location of the server SSL private key (.pem).
--node-ssl-cert <file> location of the client SSL certificate (.pem)
(Used to verify this node to other servers.)
--server-ssl-certificate FILE
Location of the server SSL certificate (.pem).
--ssl-ca <file> location of the CA certificate (.pem)
--client-ssl-private-key FILE
Location of the client SSL private key (.pem).
--client-ssl-certificate FILE
Location of the client SSL certificate (.pem).
Snapshot
--snapshot-save-path DIRECTORY
Directory under which to store snapshots of suspended scans.
```
Clone repository

Pages [all]

  • Home
  • Installation instructions
  • For users
    • Executables
    • Command Line Interface
    • Web User Interface
    • Distributed components (Dispatchers and Instances)
      • RPC Client
      • RPC Server (Dispatcher)
  • For developers
    • Core API documentation
    • RPC API
    • Development environment

Can't find what you're looking for? Why not have a look at the support portal?