From: Alexander Dietrich <alexander@dietrich.cx>
To: Galene Mailing List <galene@lists.galene.org>
Subject: [Galene] Thoughts on global user passwords
Date: Sat, 26 Sep 2026 15:50:39 +0200 (CEST) [thread overview]
Message-ID: <875895670.207844.1790430639655@app.mailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hello,
I've been experimenting with Galene recently, and really like it so far! Except for the part where you potentially have to create the same "op" user accounts in a bunch of groups, each with their own but identical password. (At least that's my understanding of the current system.)
I was wondering what you think about adding the ability to store usernames/passwords for regular users in the "users" map of "data/config.json"? Galene could use these for password authentication when a user has permissions for a particular group, but no group-specific password.
There's a thread called "User management" from 2021 in the archives which discussed similar ideas, but for my use case I would ideally like to work without any additional tools or services.
Kind regards,
Alexander
[-- Attachment #2: Type: text/html, Size: 1297 bytes --]
reply other threads:[~2026-09-26 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=875895670.207844.1790430639655@app.mailbox.org \
--to=alexander@dietrich.cx \
--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