Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Marty Betz <martybetz@gmail.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Admin group creation
Date: Mon, 02 Dec 2024 20:12:49 +0100	[thread overview]
Message-ID: <87plm9gaq6.wl-jch@irif.fr> (raw)
In-Reply-To: <CAK0PynfZCYjRS7JLpT5Sa542368RW86tq1Qy9heL+RnYLM-wCw@mail.gmail.com>

> On further investigation, it seems the group config parameters "presenter" and
> "wildcard-user" interact in a non-trivial way.

There are two syntaxes for Galene group definitions: the old syntax, based
on pattern-matching, used in Galene 0.8 and earlier; and the new syntax,
based on a straightforward map from usernames to user descriptions, which
was introduced in Galene 0.9.

Galene still parses the old syntax for compatibility reasons.  You're
mixing the two syntaxes, which is confusing.  Please don't do that.  The
following fields are now deprecated:

  - "op", "presenter" and "other", replaced by "users";
  - "allow-subgroups" and "allow-anonymous", no longer supported.

> Having "presenter":[{}] seems to act like a wildcard user authenticator,

Yes.  That's the old syntax for what is now

   "wildcard-user": {"password":{"type":"wildcard"}, "permissions":"presenter"}

The new syntax is more verbose by design, so that you don't open your
server by mistake.

> unless another "wildcard-user" field is present.

If you mix the two syntaxes in contradictory manners, the new syntax takes
precedence over the old one.  There should be a warning in the log.

-- Juliusz


  reply	other threads:[~2024-12-02 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01 23:17 [Galene] " Marty Betz
2024-12-02 12:08 ` [Galene] " Juliusz Chroboczek
2024-12-02 17:28   ` Marty Betz
2024-12-02 18:00     ` Marty Betz
2024-12-02 19:12       ` Juliusz Chroboczek [this message]
2024-12-02 19:56         ` Marty Betz

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=87plm9gaq6.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --cc=martybetz@gmail.com \
    /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