django-simplesshkey 1.0.0

Associates multiple SSH public keys with Django user accounts (fork of django-sshkey without SSHD integration)

===================
django-simplesshkey
===================

django-simplesshkey allows you to associate multiple SSH public keys with Django
user accounts. It provides views to list, add, edit, and delete keys, each of
which is intended for end-user consumption. Of course, you can also manage SSH keys
from the administration itnerface.

SSH keys are simply stored in the Django database, and what you do with them is
up to you: you can have a cron job that regularly dumps SSH keys to files, or
connect a signal to take an action each time a SSH key is saved...
For instance, the author uses ansible to deploy the SSH keys to several machines.


About django-sshkey and django-simplesshkey
===========================================

`django-simplesshkey` is a fork of django-sshkey_, based on version 2.5.0.

The goal of this fork is twofolds:

* Keep only basic functionalities needed to manage SSH keys linked to Django
users. In particular, the optional integration with OpenSSH has been
completely removed, which simplifies configuration and avoids leaking
information by default (public lookup view). Also, sending emails when
keys are added or modified is no longer done, because it can easily be
implemented outside of this application.

* Be more flexible: impose less constraints on the model (no unicity),
allow to override some fields of the model or form. Also, sending emails
outside of this application obviously allows more flexibility.

Of course, if you need all the extra features of django-sshkey, you should
continue using it!

Migrating from django-sshkey
============================

If you are using django-sshkey but don't need the extra functionalities, it is
possible to start using django-simplesshkey and import your data.

The migration process is a bit convoluted, see `README.upgrading.rst` for details.


The Django app
==============

To use django-sshkey in your Django project, simply add ``django_sshkey`` to
``INSTALLED_APPS`` in ``settings.py``, map the URLs into your project, and
provide templates for the views (example templates are provided in the source).


URL Configuration
-----------------

This text assumes that your project's ``urls.py`` maps ``simplesshkey.urls``
into the URL namespace as follows::

urlpatterns = [
...
url('^sshkey/', include('simplesshkey.urls')),
...
]

You will need to adjust your URLs in the examples below if you use a different
mapping.


Settings
--------

``SSHKEY_AUTHORIZED_KEYS_OPTIONS``
String, optional. Defines the SSH options that will be prepended to each
public key. ``{username}`` will be replaced by the username; ``{key_id}``
will be replaced by the key's id. New in version 2.3.

``SSHKEY_ALLOW_EDIT``
Boolean, defaults to ``False``. Whether or not editing keys is allowed.
New in version 2.3.

``SSHKEY_DEFAULT_HASH``
String, either ``sha256``, ``md5``, or ``legacy`` (the default). The default
hash algorithm to use for calculating the finger print of keys. Legacy
behavior enforces OpenSSH's pre-6.8 behavior of MD5 without the ``MD5:``
prefix. New in version 2.5.


Templates
---------

Example templates are available in the ``templates.example`` directory.

``sshkey/userkey_list.html``
Used when listing a user's keys.

``sshkey/userkey_detail.html``
Used when adding or editing a user's keys.


Management commands
-------------------

``import_sshkey [--auto-resolve] [--prefix PREFIX] [--name NAME] USERNAME KEY_PATH ...``
Imports SSH public keys to tie to a user. If ``--auto-resolve/-a`` are given,
attempt to generate unique key names using a UUID. The prefix used during
this process is the key name, but can be changed using ``--prefix/-p``.

``normalize_sshkeys [USERNAME KEY_NAME]``
Recalculates key data to reflect a changed setting, for instance, if you have
changed ``SSHKEY_DEFAULT_HASH`` and some keys have incorrect fingerprints in
your database. Given no arguments, all keys will be normalized. The username
asnd key name are optional, and if specified, will limit affected keys to
those owned by a user, or a particular key of a user. This can also be done
via the administration panel, but if you have a large key database the
request could end up timing out.


.. _djangosshkey: https://github.com/ClemsonSoCUnix/django-sshkey