From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 46049@debbugs.gnu.org
Subject: [bug#46049] [PATCH] services: nginx: Add ssl-protocols option.
Date: Sun, 24 Jan 2021 14:25:32 +0100 [thread overview]
Message-ID: <01fc7a42-eba3-aaf6-783c-778cddf69b51@web.de> (raw)
In-Reply-To: <874kj7qfo5.fsf@nckx>
On 24.01.21 02:36, Tobias Geerinckx-Rice wrote:
> Jonathan Brielmaier 写道:
>> The default settings is accordingly to Mozillas "Intermediate"
>> configuration for nginx: https://ssl-config.mozilla.org
>
> Oh, I see! Hiding subjective tweaks to upstream defaults in Guix
> services is a bad idea.
>
> Imagine debugging this at 2 a.m., staring at the official nginx
> documentation through your tears.
I see your point, but I usually start with the Guix service
documentation and it clearly would state "TLSv1.2 TLSv1.3". If your
client doesn't support TLSv1.2 (thats 12 years old), it's maybe a better
idea to fallback to HTTP...
I think in general its a good idea to follow upstreams default, but it
should not hinder us to make more secure defaults
>> I would also like to implement an option with good defaults for
>> `ssl_ciphers` if you have ideas how to do that in a nice way speak up :)
>
> How about writing ‘mozilla-recommended’ nginx configuration presets that
> users can inherit from? This would imply keeping them up to date,
> including the specific versions of nginx and *ssl in Guix.
Hm, I try to keep stuff simple and to be honest all those service
"matroska" stuff grows over my head. If theres an error I can not debug
them at 2am or at any other time...
A compromise would maybe something like :
(ssl-protocols %upstream-default OR %mozilla-default OR "Your custom
string")
next prev parent reply other threads:[~2021-01-24 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 10:00 [bug#46049] [PATCH] services: nginx: Add ssl-protocols option Jonathan Brielmaier
2021-01-23 10:07 ` Jonathan Brielmaier
2021-01-24 1:36 ` guix-patches--- via
2021-01-24 13:25 ` Jonathan Brielmaier [this message]
2021-01-24 0:45 ` guix-patches--- via
2022-11-22 15:26 ` mirai
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01fc7a42-eba3-aaf6-783c-778cddf69b51@web.de \
--to=jonathan.brielmaier@web.de \
--cc=46049@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).