Skip to content
CURSE is an SSH certificate signing server, built as an alternative to Netflix's BLESS tool, but without a dependency on AWS.
Go Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cursed Fixed tls cert generation bug Apr 2, 2017
jinx
.gitignore
.travis.yml
INSTALL.md Deprecated manual install instructions (need to update for 0.8) Feb 25, 2017
LICENSE Updated license Feb 28, 2017
README.md

README.md

CURSE

CURSE is an SSH certificate signing server, built as an alternative to Netflix's BLESS tool, but without a dependency on AWS.

Demo

gif

This software is currently in a beta state, feel free to submit issues on GitHub with any suggestions for improvement/feature requests or issues encountered.

Table of Contents

Requirements

  • OpenSSH 5.6+
  • CentOS 7
  • Ubuntu 14.04+ (Destination servers)
  • Ubuntu 15.10+ (Server running CURSE daemon)
  • Debian 7+ (Destination servers)
  • Debian 8+ (Server running CURSE daemon)

Because SSH certificates are a relatively recent feature in OpenSSH, older versions of CentOS unfortunately do not support their use.

Install

These instructions assume the bastion host is hosting the curse daemon. Adjust instructions as necessary if hosting cursed on another server.

Ubuntu/Debian

Ubuntu 15.10+/Debian 8+

First, install the debian repo and GPG key:

$ sudo sh -c 'echo "deb http://mirror.go-repo.io/curse/deb/ curse main" >/etc/apt/sources.list.d/curse.list'
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 0732065B92735F2F

Update and install pwauth, curse and jinx:

$ sudo apt-get update && sudo apt-get install curse jinx pwauth

Run the curse post-install setup script

$ sudo bash /opt/curse/sbin/setup.sh

This will output your CA public key to be added to destination servers, and setup the curse daemon for running.

If all went well you should now be able to request certificates:

$ jinx echo test
$ ssh-keygen -Lf ~/.ssh/id_jinx-cert.pub

Now, all that is left is to add the CA public key on the servers you want to connect to:

Add TrustedUserCAKeys /etc/ssh/cas.pub to /etc/ssh/sshd_config on your destination servers and Put the contents of /opt/curse/etc/user_ca.pub into your /etc/ssh/cas.pub on the destination server.

Netflix recommends generating several CA keypairs and storing the private keys of all but one offline, in order to simplify CA key rotation. If you choose to do this you will want to also add the pubkeys of all of your CA keypairs to the /etc/ssh/cas.pub file at this time as well.

CentOS

CentOS 7

First, install pwauth, curse, and jinx:

$ sudo rpm --import https://mirror.go-repo.io/curse/centos/RPM-GPG-KEY-GO-REPO
$ sudo curl -s https://mirror.go-repo.io/curse/centos/curse-repo.repo | tee /etc/yum.repos.d/curse-repo.repo
$ sudo yum install curse jinx pwauth

Unless you're using httpd on this server for any other reason you should mask the httpd service:

$ sudo systemctl mask httpd

Run the curse post-install setup script

$ sudo bash /opt/curse/sbin/setup.sh

This will output your CA public key to be added to destination servers, and setup the curse daemon for running.

If all went well you should now be able to request certificates:

$ jinx echo test
$ ssh-keygen -Lf ~/.ssh/id_jinx-cert.pub

Now, all that is left is to add the CA public key on the servers you want to connect to:

Add TrustedUserCAKeys /etc/ssh/cas.pub to /etc/ssh/sshd_config and Put the contents of /opt/curse/etc/user_ca.pub into your /etc/ssh/cas.pub on the destination server.

Netflix recommends generating several CA keypairs and storing the private keys of all but one offline, in order to simplify CA key rotation. If you choose to do this you will want to also add the pubkeys of all of your CA keypairs to the /etc/ssh/cas.pub file at this time as well.

TODO

  • Authentication
  • Document Authentication Setup
  • SSL support
  • Add support for maximum pubkey ages in daemon
  • Client app
  • More configuration options
  • Add support for maximum pubkey ages in client and automatic key regeneration
  • Add support for key algorithm enforcement/auto-key-generation
  • RPM/DEB packages for easier installation
  • Per-user access ACLs

Maybe Someday

  • Interactive ssh client for command logging
You can’t perform that action at this time.