Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: galene@lists.galene.org
Subject: [Galene] wildcard users
Date: Mon, 2 Nov 2026 12:12:04 +0100	[thread overview]
Message-ID: <362CEC86-2063-4E6F-A30A-5C0AEABB5FF9@webweaving.org> (raw)

I am currently allowing people to enter an arbitrary name (and no password) on certain calls with a definition such as:

	// Generated 2026-11-02 11:09:23 UTC, project bar-test, DB: 9656dfdac01ba854402ca635e
	{
	  "public": false,
	  "op": [
		    {
		      "username": "xxxchairpersonxxx",
		      "password":  {"type":"bcrypt","key":"XXX"}
		    }
 	 ],
	  "users": {
		"XXXXmoderator1XXX":{"permissions": "present",....},
  		"XXXXmoderator2XXX":{"permissions": "present",....}
	  },
	  "wildcard-user": {
		"password": "",  "permissions": "present"
	  },
	  "presenter": [
	    {}
	  ]
	}

And am now seeing 

	Nov  2 03:56:52 jailed-galene daemon[19372]: 
		2026/11/02 03:56:52 /var/db/galene/groups/XXXXXXXX.json: duplicate wildcard user 
			2026/11/02 03:56:52 /var/db/galene/groups/XXXXXXXXX.json: duplicate wildcard user

in my log. Why is this ? And what is the right way to allow arbitrary names (and an empty or fixed, simple PIN style, password for ad-hoc cases where sending an invite or similar hurdle/extra step is non ideal) ?

With kind regards,

Dw

             reply	other threads:[~2026-11-02 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 11:12 Dirk-Willem van Gulik [this message]
2026-11-02 12:05 ` [Galene] Re: wildcard users Juliusz Chroboczek
2026-11-02 12:13   ` Dirk-Willem van Gulik
2026-11-02 12:27     ` 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=362CEC86-2063-4E6F-A30A-5C0AEABB5FF9@webweaving.org \
    --to=dirkx@webweaving.org \
    --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