From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Heads up: management protocol
Date: Wed, 10 Apr 2024 13:06:51 +0200 [thread overview]
Message-ID: <87wmp5v5mc.wl-jch@irif.fr> (raw)
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
next reply other threads:[~2024-04-10 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 11:06 Juliusz Chroboczek [this message]
2024-04-10 12:02 ` [Galene] " Dianne Skoll
[not found] ` <171275058535.1000.9334285592739539641@gauss.local>
2024-04-10 12:12 ` Juliusz Chroboczek
2024-04-10 12:33 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmp5v5mc.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox