This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description


This tool provides a command-line client for BroBox One, a Bro appliance engineered from the ground up by Bro’s creators to transform network traffic into high-fidelity data for your analytics pipeline. Using the command-line client, you can configure and control a BroBox remotely through its comprehensive RESTful API. See the BroBox documentation for an extended version of this client overview.

Author:Broala <>


This client is open-source under a BSD license. See COPYING for details.


The command-line client needs Python >= 3.4 with the requests module installed as its main dependency.

The easiest way to install the client is through the Python Package Index:

# pip3 install brobox-client

Alternatively, you can install the latest version from GitHub:

# git clone
# cd brobox-client
# python3 install

If everything is installed correctly, --help will give you a usage message:

# brobox --help
Usage: brobox [<global options>] <command> <subcommand> [<options>]
          [--ssl-ca-cert SSL_CA_CERT] [--ssl-no-verify-certificate]
          [--ssl-no-verify-hostname] [--cache CACHE]

Note that initially, --help will not yet show you any further commands to use. Proceed to the next section to let the client connect to your device.

Access and Authentication

You need to enable access to the BroBox API through the device’s configuration interface. You also need to set passwords for the API users admin (for unlimited access) and monitor (for read-only access). See the BroBox documentation for more information.

Next, you need to tell the brobox client the network address of your BroBox. You have three choices for doing that:

  • Add -b <address> to the command-line.
  • Create a configuration file ~/.broboxrc with the content brobox=<address>.
  • Set the environment variable BROBOX=<address>.

If that’s all set up, brobox --help will now ask you for a username and password, and then show you the full list of commands that the device API enables the client to offer. If you confirm saving the credentials, the client will store them in ~/.brobox/credentials for future reuse. You can also specify authentication information through the Configuration File or as Global Options.


The client offers the API’s functionality through a set of commands of the format <command> <subcommand> [options]. By adding --help to any command, you get a description of all its functionality and options.

If the --help output lists a command’s option as being of type file, the client requires you to specify the path to a file to send. In addition, you can prefix any option’s value with file:// to read its content from a file instead of giving it on the command-line itself.

(Note: The --help output will contain the list of commands only if the client can connect, and authenticate, to the device.)

Global Options

The brobox client support the following global command-line options with all operations:

Does not wait for asynchronous commands to complete before exiting.
Specifies the network address of the BroBox device.
Sets a custom file for caching BroBox meta data.
Enables debugging output showing HTTP requests and replies.
Specifies the password for authentication.
Specifies a file containing a custom SSL CA certificate for validating the device’s authenticity.
Instructs the client to accept any BroBox device SSL certificate.
Instructs the client to accept the BroBox’s device SSL certificate even if it does not match its hostname.
Specifies the user name for authentication.
Displays the version of the brobox client and exits.

Configuration File

The brobox clients looks for a configuration file ~/.broboxrc. The file must consist of lines <key>=<value>. Comments starting with # are ignored. brobox support the following keys:

The network address of the BroBox device.
The user name for authentication.
The password for authentication.
A file containing a custom SSL CA certificate for validating the device’s authenticity.
If set to false, the client will accept any BroBox device SSL certificate.
If set to false, the client will accept the BroBox’ device SSL certificate even if it does not match its hostname.
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
brobox_client-1.0.2-py3-none-any.whl (27.2 kB) Copy SHA256 Checksum SHA256 py3 Wheel Jun 30, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting