Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene]  Heads up: Galène generates self-signed certificates
Date: Wed, 24 Feb 2021 20:30:22 +0100	[thread overview]
Message-ID: <87mtvtqn5d.wl-jch@irif.fr> (raw)

Hi,

While fixing https://github.com/jech/galene/issues/13, I implemented
automatic generation of self-signed certificates if a certificate is not
found in the data/ directory.  In short:

1. If you're currently using a real certificate (stored in data/cert.pem
   and data/key.pem), there's nothing to do.  The only difference is that
   Galène will notice when you update the certificate, and load the new
   certificate automatically.

2. If you're currently using a self-signed certificate, you may remove it:
   Galène will notice that there is no certificate, and generate
   a self-signed certificate in memory (the certificate is never written
   to disk, as usual in Galène).

The self-signed certificate uses 2048-bit RSA, which I understand is
compatible with all browsers.  I could easily generate ed25519 or P-256
instead, if you understand the crypto please let me know what to do.

I've tested that my self-generated certificate works with Chromium and
Firefox.  Please let me know if you think there's something wrong.

-- Juliusz

             reply	other threads:[~2021-02-24 19:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 19:30 Juliusz Chroboczek [this message]
2021-02-24 19:47 ` [Galene] " Michael Ströder
2021-02-24 21:16   ` Juliusz Chroboczek
2021-02-24 21:24     ` Juliusz Chroboczek
2021-02-24 21:29       ` Dave Taht
2021-02-24 21:55         ` Toke Høiland-Jørgensen
2021-02-24 21:57         ` Michael Ströder
2021-02-24 22:25           ` Juliusz Chroboczek
2021-02-24 22:02         ` Juliusz Chroboczek
2021-02-24 21:44     ` Michael Ströder

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=87mtvtqn5d.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --subject='Re: [Galene]  Heads up: Galène generates self-signed certificates' \
    /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