all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 46049@debbugs.gnu.org
Subject: [bug#46049] [PATCH] services: nginx: Add ssl-protocols option.
Date: Sun, 24 Jan 2021 02:36:42 +0100	[thread overview]
Message-ID: <874kj7qfo5.fsf@nckx> (raw)
In-Reply-To: <5d511a10-e589-7de9-35ed-8294298dee7a@web.de>

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

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 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.

I don't know whether this belongs in Guix or not, but then we 
already ship someone's Facebook blocklist, so... :-)

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-01-24  1:37 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 [this message]
2021-01-24 13:25     ` Jonathan Brielmaier
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kj7qfo5.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=46049@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.