[Galene] Heads up: management protocol

[Juliusz Chroboczek <jch@irif.fr>]

Hi,

Currently, the right was to write a management interface for Galene is to
directly edit the on-disk configuration files.  This is tricky to do
right, and somewhat fragile, since multiple processes are accessing the
same files.

I've almost finishes implementing an HTTP interface for managing Galene,
which will hopefully make it easier to manage remotely.  I'm planning to
merge it into master before the week-end (it currently lives in branch
"api").

# Get the list of groups

    GET /galene-api/.groups/

# Get a group's configuration

    GET /galene-api/.groups/groupname

This returns a "sanitised" configuration, without any cryptographic keys
or user descriptions.

# Create a new group

    PUT /galene-api/.groups/groupname
    If-None-Match: *

The If-None-Match header avoids overwriting an existing group.

# Edit a group definition

    GET /galene-api/group/groupname

    (edit the returned JSON)

    PUT /galene-api/.groups/groupname
    If-Match: (the etag returned by the GET above)

The If-Match header avoids overwriting changes made by a different client
in the meantime.

# Create a new user

    PUT /galene-api/.groups/groupname/.users/username
    If-None-Match: *

This creates a user entry with an invalid password.  You need to set
a password in a separate step.

# Set a user's password, server-side hashing

    POST /galene-api/.groups/groupname/.users/username/.password

This hashes the password on the server.  There is currently no way to set
the hashing algorithm (we use 4096 iterations of PBKDF2, which is very weak).

# Set a user's password, client-side hashing

    PUT /galene-api/.groups/groupname/.users/username/.password

-- Juliusz