Creating Certs

Bumper requires specially crafted certificates to work properly. In the spirit of security, Bumper will not ship with default certificates. Users will need to generate and provide their own certificates.

Certificates should be placed in the {bumper_home}/certs directory. If certificates are located elsewhere environment variables can be set that point to their location.

Users can generate certificates in the following ways:

Method	Description
Create_Certs	(Preferred) This is a utility that has been created to assist in generating the certificates required easily.
OpenSSL	Users can manually create the same certificates as Create_Certs by utilizing OpenSSL.
Custom CA/Self	If a user has their own CA the certificates can be generated there and used within Bumper.

Certificate Requirements:

A CA Cert must be provided that can be imported into devices (phones, browsers, etc).
Server certificate should include SANs (Subject Alternate Names) for all of the *.ecovacs, etc domains.

Creating certs using Create_Certs

Create_Certs was created to ease creation of certificates specifically for Bumper. Binaries are provided for Windows/Linux/OSX/RPi (ARMv5) in the Create_Certs directory.

Binary	Platform
create_certs_linux	Linux
create_certs_osx	macOS/x
create_certs_windows.exe	Windows
create_certs_rpi	RaspberryPi (ARM v5)

Create_Certs is written in Go which allows cross-platform compiling. If the binaries don't work on your platform, install Go.

With Go installed you can:

Execute the go code - go run create_certs/src/create_certs.go
Build a new binary for your platform - go build create_certs/src/create_certs.go

Usage

Create_Certs will automatically create the required certificates in the directory it is executed from. For best results change to the {bumper_home}/certs directory prior to executing, otherwise you'll need to move the certs after.

cd certs
Execute create_certs (using the binary fitting your platform) - ../create_certs/create_certs_{platform}
The certificates are generated and should be available in the current directory (certs)

Subject Alternative Name

The server certificate requires a number of SAN (Subject Alternative Names) be added. Create_Certs handles this automatically by loading any SANs listed in the create_certs/Bumper_SAN.txt file. If creating certificates manually via OpenSSl/Custom CA these will need to be added.

Manually create certs with OpenSSL

I get it, you don't trust create_certs and want to do it manually. The easiest way to create the required certs is at https://certificatetools.com/. In fact the below OpenSSL commands come straight from that site, post creation via the GUI.

Create a Root CA

Create csrconfig.txt for use in later commands

csrconfig.txt

[ req ]
default_md = sha256
prompt = no
req_extensions = req_ext
distinguished_name = req_distinguished_name
[ req_distinguished_name ]
commonName = Bumper CA
organizationName = Bumper
[ req_ext ]
keyUsage=critical,keyCertSign,cRLSign
basicConstraints=critical,CA:true,pathlen:1

Create certconfig.txt for use in later commands

certconfig.txt

[ req ]
default_md = sha256
prompt = no
req_extensions = req_ext
distinguished_name = req_distinguished_name
[ req_distinguished_name ]
commonName = Bumper CA
organizationName = Bumper
[ req_ext ]
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
keyUsage=critical,keyCertSign,cRLSign
basicConstraints=critical,CA:true,pathlen:1

Generate the RSA private key

openssl genpkey -outform PEM -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out priv.key
Create the CSR

openssl req -new -nodes -key priv.key -config csrconfig.txt -out cert.csr
Self-sign your CSR

openssl req -x509 -nodes -in cert.csr -days 3650 -key priv.key -config certconfig.txt -extensions req_ext -out cert.crt

Create the Server Certificate

Create csrconfig.txt for use in later commands