unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Leo Famulari <leo@famulari.name>,bo0od <bo0od@riseup.net>
Cc: 47823@debbugs.gnu.org
Subject: bug#47823: Hardenize Guix website TLS/DNS
Date: Fri, 16 Apr 2021 20:10:11 -0400	[thread overview]
Message-ID: <4BF8EE8A-C2B4-429A-A0DF-928155A5802E@lepiller.eu> (raw)
In-Reply-To: <YHm4HTDJwTfXFI3U@jasmine.lan>

Le 16 avril 2021 12:15:25 GMT-04:00, Leo Famulari <leo@famulari.name> a écrit :
>On Fri, Apr 16, 2021 at 11:00:05AM +0000, bo0od wrote:
>> Scanning Guix website gave many missing security features which
>modern
>> security needs them to be available:
>> 
>> * TLS and DNS:
>> 
>> looking at:
>> 
>> https://www.hardenize.com/report/guix.gnu.org/1618568751
>> 
>> https://www.ssllabs.com/ssltest/analyze.html?d=guix.gnu.org
>
>Thanks!
>
>> - DNS: DNSSEC support missing (important)
>
>Hm, is it important? My impression is that it's an idea whose time has
>passed without significant adoption.
>
>But maybe we could enable it if the costs are not too great.

gnu.org does not have dnssec, so we'd need them to work on that first.




  parent reply	other threads:[~2021-04-17  0:11 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
2021-04-17  0:10   ` Julien Lepiller [this message]
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=4BF8EE8A-C2B4-429A-A0DF-928155A5802E@lepiller.eu \
    --to=julien@lepiller.eu \
    --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).