Command line and Web Service Random Password Generator written in GO
Clone or download
Latest commit f91977c Oct 15, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources New default port and cross-paltform test Sep 13, 2017
src Update goling and gosec Oct 15, 2018
.gitignore Refactoring - server mode only Apr 7, 2017
.travis.yml Update pip as sudo Oct 15, 2018 Various fixes Apr 7, 2017
LICENSE Refactoring - server mode only Apr 7, 2017
Makefile Update goling and gosec Oct 15, 2018 Remove develop branch Oct 15, 2018
RELEASE Initial commit Nov 19, 2015
VERSION Update goling and gosec Oct 15, 2018 Refactoring - server mode only Apr 7, 2017


Command-line and Web-service Random Password Generator

Master Branch Master Build Status Master Coverage Status Go Report Card

Donate via PayPal Please consider supporting this project by making a donation via PayPal


An additional Python program is used to check the validity of the JSON configuration files against a JSON schema:

sudo pip install json-spec 


Web-service Random Password Generator

This is a full example of command-line and Web-service GO language project using a Makefile that integrates targets for common QA tasks and packaging, including RPM, Debian and Docker.

Quick Start

This project includes a Makefile that allows you to test and build the project in a Linux-compatible system with simple commands.
All the artifacts and reports produced using this Makefile are stored in the target folder.

All the packages listed in the resources/DockerDev/Dockerfile file are required in order to build and test all the library options in the current environment. Alternatively, everything can be built inside a Docker container using the command "make dbuild".

To see all available options:

make help

To build the project inside a Docker container (requires Docker):

make dbuild

An arbitrary make target can be executed inside a Docker container by specifying the "MAKETARGET" parameter:

MAKETARGET='qa' make dbuild

The list of make targets can be obtained by typing make

The base Docker building environment is defined in the following Dockerfile:


To execute all the default test builds and generate reports in the current environment:

make qa

To format the code (please use this command before submitting any pull request):

make format

Useful Docker commands

To manually create the container you can execute:

docker build --tag="tecnickcom/rndpwddev" .

To log into the newly created container:

docker run -t -i tecnickcom/rndpwddev /bin/bash

To get the container ID:

CONTAINER_ID=`docker ps -a | grep tecnickcom/rndpwddev | cut -c1-12`

To delete the newly created docker container:

docker rm -f $CONTAINER_ID

To delete the docker image:

docker rmi -f tecnickcom/rndpwddev

To delete all containers

docker rm $(docker ps -a -q)

To delete all images

docker rmi $(docker images -q)

Running all tests

Before committing the code, please check if it passes all tests using

make qa

Other make options are available install this library globally and build RPM and DEB packages. Please check all the available options using make help.


rndpwd [flags]


-c, --configDir             : Configuration directory to be added on top of the search list


If no command-line parameters are specified, then the ones in the configuration file (config.json) will be used. The configuration files can be stored in the current directory or in any of the following (in order of precedence):

  • ./
  • config/
  • $HOME/rndpwd/
  • /etc/rndpwd/

This service also support secure remote configuration via Consul or Etcd. The remote configuration server can be defined either in the local configuration file using the following parameters, or with environment variables:

  • remoteConfigProvider : remote configuration source ("consul", "etcd");
  • remoteConfigEndpoint : remote configuration URL (ip:port);
  • remoteConfigPath : remote configuration path where to search fo the configuration file (e.g. "/config/rndpwd");
  • remoteConfigSecretKeyring : path to the openpgp secret keyring used to decript the remote configuration data (e.g. "/etc/rndpwd/configkey.gpg"); if empty a non secure connection will be used instead;

The equivalent environment variables are:


Server Mode

When the server mode is enabled a RESTful HTTP JSON API server will listen on the configured address:port for the following entry points:

/ GET return a list of available entry points and tests
/status GET check the server status
/password GET generate new passwords as configured; charset, length and quantity can be specified as query parameters


This service logs the log messages in JSON format:


Developer(s) Contact