From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; dkim=pass header.d=irif.fr header.i=@irif.fr header.a=rsa-sha256 header.s=dkim-irif header.b=jalTv9IQ; arc=none (Message is not ARC signed); dmarc=none Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by mail.toke.dk (Postfix) with ESMTPS id 59C8D17030CC for ; Sat, 26 Sep 2026 18:05:54 +0200 (CEST) Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 68QG5k7f013696; Sat, 26 Sep 2026 18:05:46 +0200 Received: from mailhub.math.univ-paris-diderot.fr (unknown [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0125C341F5; Sat, 26 Sep 2026 18:05:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=irif.fr; h= content-type:content-type:mime-version:user-agent:references :in-reply-to:subject:subject:from:from:message-id:date:date :received:received; s=dkim-irif; t=1790438745; x=1791302746; bh= cERjOqMF00UmOXjlpshYRvwIX9U6xsKZufAkSpEY178=; b=jalTv9IQAx53qoDJ gsKcjaN+6fFsZZqveiE4jk8Dihjsgi05o//DV+UArXomIdFgyZuWsYHS6vsMVOye 43ylZHWgSD5u768dmfFKspL1wcCU6miCKgdwppYvQfenT2u4gtZeHYYw1/1xnzuk AU7XkhXzuEPWBHZMuLFdw5UivgwqnwNAYPAUJKPURbb7F7L/AvxW/5gy3cr5a0HO Nb2tVZJVar27cVGq3PTc5w/Il6sS7zi2WuMhqyRKF4iwK9bJmQNMppe9XUiskRsE amMT0Q9QFHxys3YqJ1IayMnAKKwYTcqgrMQxwt6xclYnDpuZCZoN+3rm87xEkg12 ltfdHw== X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id JCcdagEjorQZ; Sat, 26 Sep 2026 18:05:45 +0200 (CEST) Received: from trurl.irif.fr (unknown [82.64.191.149]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E57B334315; Sat, 26 Sep 2026 18:05:44 +0200 (CEST) Date: Sat, 26 Sep 2026 18:05:44 +0200 Message-ID: <877bk86lrb.wl-jch@irif.fr> From: Juliusz Chroboczek To: Alexander Dietrich Cc: Galene Mailing List In-Reply-To: <179043064484.1076.1779405941341360418@gauss> References: <179043064484.1076.1779405941341360418@gauss> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/30.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 26 Sep 2026 18:05:46 +0200 (CEST) X-Miltered: at korolev with ID 6AB7ED5A.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 6AB7ED5A.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 6AB7ED5A.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham Message-ID-Hash: TDQXZQSRHIOW2QY4E3PG572JP4TBOW3W X-Message-ID-Hash: TDQXZQSRHIOW2QY4E3PG572JP4TBOW3W X-MailFrom: jch@irif.fr X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Galene] Re: Thoughts on global user passwords List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > 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.) Yes. The reason it's not a problem for me is that I generally create a whole hierarchy (using the "auto-subgroups" functionality) rather than a distinct group for every task. > 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"? I've thought about it, but it's not that easy: - data/config.json is read-only, so it won't be possible to add new global users through the API; - you'd probably want users that only exist in a subhierarchy, for example a user that's an op in all groups under "group/teaching/*". So my take would be to create a database of users, similar to the token database. I encourage you to design and implement a proof of concept, but please be aware that it'll likely not be merged until we find satisfactory answers to the questions above (and others). -- Juliusz