From: Juliusz Chroboczek <jch@irif.fr>
To: "Michael Ströder" <michael@stroeder.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Heads up: Galène generates self-signed certificates
Date: Wed, 24 Feb 2021 22:24:58 +0100 [thread overview]
Message-ID: <87ft1lqhud.wl-jch@irif.fr> (raw)
In-Reply-To: <87im6hqi83.wl-jch@irif.fr>
>> If at least one of cert.pem and key.pem are present
> Currently, we fall back to the self-signed certificate if either of the
> two files is missing. Could you please describe the kind of attacks that
> you're worried about?
I've changed the behaviour in that case -- we'll fail the connection if
only one of the two files exists.
next prev parent reply other threads:[~2021-02-24 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:30 [Galene] " Juliusz Chroboczek
2021-02-24 19:47 ` [Galene] " Michael Ströder
2021-02-24 21:16 ` Juliusz Chroboczek
2021-02-24 21:24 ` Juliusz Chroboczek [this message]
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=87ft1lqhud.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=michael@stroeder.com \
--subject='[Galene] Re: 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