Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: "Timothée Jaussoin" <edhelas@movim.eu>
Cc: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: Galene HTTP API error and various feedback
Date: Sat, 11 Jul 2026 15:07:30 +0200	[thread overview]
Message-ID: <AC10EAE0-BB1A-4690-A559-8E56F04F5049@webweaving.org> (raw)
In-Reply-To: <9342d9f8-42e6-4a9b-88d0-dc05ac7bd561@movim.eu>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

On 11 Jul 2026, at 15:04, Timothée Jaussoin <edhelas@movim.eu> wrote:
> Le 11/07/2026 à 12:50, Juliusz Chroboczek a écrit :
...
>>     sed "s/@PASSWORD@/$pw/" < /etc/galene.conf.template > /tmp/galene.conf
>>     galene -c /tmp/galene.conf
>> 
>> So I'm not too keen to add code that I'm going to have to maintain forever
>> just to avoid a few lines of shell.  Is there any reason why you need this
>> to be done within the server itsef?
> Having something like DotEnv (https://www.dotenv.org/docs/) to configure Galene would even be better. Then you can launch it using a standard file and environnement variable (which is really useful when you wrap it in containers :)).

I'd be a bit cautious when it comes to putting secrets in ENV variables (or passing them on the command line) -- as they can leak via an strategic `ps -aux, -elwf, etc) or via a well meaning Nagions, SNMP or other monitoring system.

Best to pass these by root-protected files, via socket/device or on a file descriptor -- e.g. see openssl or pgp/gpg for examples.

With kind regards,

Dw 


[-- Attachment #2: Type: text/html, Size: 1815 bytes --]

  reply	other threads:[~2026-07-11 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 15:43 [Galene] Galene HTTP API error and various feedback Timothée Jaussoin
2026-07-11 10:50 ` [Galene] " Juliusz Chroboczek
2026-07-11 13:04   ` Timothée Jaussoin
2026-07-11 13:07     ` Dirk-Willem van Gulik [this message]
2026-07-11 15:02     ` Timothée Jaussoin

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=AC10EAE0-BB1A-4690-A559-8E56F04F5049@webweaving.org \
    --to=dirkx@webweaving.org \
    --cc=edhelas@movim.eu \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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