From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Michael Ströder" <michael@stroeder.com>, galene@lists.galene.org
Subject: [Galene] Re: Is the passwd file still needed?
Date: Fri, 19 Feb 2021 12:48:13 +0100 [thread overview]
Message-ID: <8735xsl1mq.fsf@toke.dk> (raw)
In-Reply-To: <b73fbdce-398a-6d89-85e3-9c8d17defe85@stroeder.com>
Michael Ströder <michael@stroeder.com> writes:
> On 2/19/21 10:52 AM, Toke Høiland-Jørgensen wrote:
>> With the new hashed-password syntax in group files, user credentials are
>> stored in the JSON for each group. But there's still a mention of a
>> passwd file in the README, but marked as 'optional' - is this still
>> needed? What's the consequence of not having it? And is there a way to
>> specify hashed passwords in that file?
>
> AFAICS it's simply used to protect the /stats page (with HTTP basic authc).
Ah, right, gotcha. I thought that just required any user with ops privs,
but I guess I got that behaviour by reusing the same user/password
combination in passwd and the groups config.
OK, so my question about using the hashed syntax remains; but maybe this
is deferred until a more complete system for user management shows up? :)
-Toke
next prev parent reply other threads:[~2021-02-19 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 9:52 [Galene] " Toke Høiland-Jørgensen
2021-02-19 10:44 ` [Galene] " Michael Ströder
2021-02-19 11:48 ` Toke Høiland-Jørgensen [this message]
2021-02-19 12:47 ` Juliusz Chroboczek
2021-02-19 13:01 ` Toke Høiland-Jørgensen
2021-02-19 13:13 ` Juliusz Chroboczek
2021-02-19 13:19 ` Gabriel Kerneis
2021-02-19 13:36 ` Toke Høiland-Jørgensen
2021-02-20 0:52 ` Juliusz Chroboczek
2021-02-20 10:06 ` Rémi Nollet
2021-02-20 11:49 ` Toke Høiland-Jørgensen
2021-02-20 12:09 ` Michael Ströder
2021-02-20 12:22 ` Toke Høiland-Jørgensen
2021-02-23 15:11 ` Dave Taht
[not found] ` <YDAEso0xTvoIg+hJ@local>
2021-02-20 12:23 ` Toke Høiland-Jørgensen
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=8735xsl1mq.fsf@toke.dk \
--to=toke@toke.dk \
--cc=galene@lists.galene.org \
--cc=michael@stroeder.com \
--subject='[Galene] Re: Is the passwd file still needed?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox