From: Felix Lechner via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 47823@debbugs.gnu.org
Cc: bo0od <bo0od@riseup.net>,
"Dr. Arne Babenhauserheide" <arne_bab@web.de>,
Marius Bakke <marius@gnu.org>,
Julien Lepiller <julien@lepiller.eu>,
Leo Famulari <leo@famulari.name>
Subject: bug#47823: Website is fine
Date: Sun, 21 May 2023 19:21:42 -0700 [thread overview]
Message-ID: <CAFHYt56qNqrRh=UT4SYtUv=GxpsbuHaM2zvzS5UVOLVc38y4tA@mail.gmail.com> (raw)
In-Reply-To: <ee41c6c6-c080-7248-eed4-a8889d0b0a28@riseup.net>
Hi,
> Scanning Guix website gave many missing security features which modern
> security needs them to be available:
While I prefer DNSSEC on my domains, I see nothing wrong with
guix.gnu.org. Presumably, some changes have been made since the bug
was filed over two years ago.
SSL Labs now rates the domain security at an A grade. For details,
please consult the attached PDF document. Hardenize.com also mentions
no issues aside from HSTS, which I consider non-essential for the Guix
website.
If there are no objections, I will close this bug in the near future. Thanks!
Kind regards
Felix
next prev parent reply other threads:[~2023-05-22 2:23 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
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 ` Felix Lechner via Bug reports for GNU Guix [this message]
2023-05-22 2:23 ` bug#47823: Website is fine 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFHYt56qNqrRh=UT4SYtUv=GxpsbuHaM2zvzS5UVOLVc38y4tA@mail.gmail.com' \
--to=bug-guix@gnu.org \
--cc=47823@debbugs.gnu.org \
--cc=arne_bab@web.de \
--cc=bo0od@riseup.net \
--cc=felix.lechner@lease-up.com \
--cc=julien@lepiller.eu \
--cc=leo@famulari.name \
--cc=marius@gnu.org \
/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.