From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Leo Famulari <leo@famulari.name>
Cc: bo0od@riseup.net, 47823@debbugs.gnu.org
Subject: bug#47823: Hardenize Guix website TLS/DNS
Date: Fri, 16 Apr 2021 23:36:15 +0200 [thread overview]
Message-ID: <875z0lap4g.fsf@web.de> (raw)
In-Reply-To: <YHm4HTDJwTfXFI3U@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Leo Famulari <leo@famulari.name> writes:
>> - Force redirection of insecure connection with plain text to TLS
>> - HSTS/HSTS-preload support missing (important)
>
> Yes, we should enable these.
Be careful with HSTS, it can make the site inaccessible if you lose
access to a certificate and have to replace it. And yes, that can happen
easily, and you then won’t have a way to inform visitors why they cannot
access the site. If you enable it, make absolutely sure that the max-age
is short enough.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-04-16 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 11:00 bug#47823: Hardenize Guix website TLS/DNS bo0od
2021-04-16 16:15 ` Leo Famulari
2021-04-16 21:36 ` Dr. Arne Babenhauserheide [this message]
2021-04-17 0:10 ` Julien Lepiller
2021-05-24 21:36 ` Marius Bakke
2021-05-25 12:51 ` bo0od
2021-05-25 13:45 ` Julien Lepiller
2021-05-25 16:37 ` bo0od
2023-05-22 2:21 ` bug#47823: Website is fine Felix Lechner via Bug reports for GNU Guix
2023-05-22 2:23 ` Felix Lechner via Bug reports for GNU Guix
2023-05-31 16:37 ` bo0od
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=875z0lap4g.fsf@web.de \
--to=arne_bab@web.de \
--cc=47823@debbugs.gnu.org \
--cc=bo0od@riseup.net \
--cc=leo@famulari.name \
/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).