From: bo0od <bo0od@riseup.net>
To: Felix Lechner <felix.lechner@lease-up.com>, 47823@debbugs.gnu.org
Cc: "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: Wed, 31 May 2023 16:37:00 +0000 [thread overview]
Message-ID: <19ed175b-856c-9c0f-4cd8-cf73f6b05ce3@riseup.net> (raw)
In-Reply-To: <CAFHYt56RRDg9KDeC+7c6KAkikXBbbPseR0i2E1cRMqUH9VUXfg@mail.gmail.com>
1- hmm? why A rate should be ok? A+ is the target that you should aim for.
Nevertheless, remove weak/stupid TLS ciphers in TLS 1.2 (e.g check
grapheneos.org in ssllab/hardenizer to see which ciphers are the
secure/recommended one to keep)
2- "While I prefer DNSSEC on my domains, I see nothing wrong with
guix.gnu.org"
Sorta contradictory, still (arguably) essential to have.
*-*-*-*
Extra fruit: in Whonix/Kicksecure and Danwin websites (i know) they
changed the certificate signature from SHA256withRSA (RSA 2048 bits) to
SHA384withECDSA (EC 384 bits) which is faster and more secure.
e.g: https://www.hardenize.com/report/whonix.org/1685550053#www_certs
This is just easy request to be made from letsencrypt and they will
issue new one for you.
Thank You!
Felix Lechner:
> On Sun, May 21, 2023 at 7:21 PM Felix Lechner
> <felix.lechner@lease-up.com> wrote:
>>
>> For details,
>> please consult the attached PDF document.
>
> Whoops, here is the missing attachment.
prev parent reply other threads:[~2023-05-31 16:38 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 ` 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 [this message]
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=19ed175b-856c-9c0f-4cd8-cf73f6b05ce3@riseup.net \
--to=bo0od@riseup.net \
--cc=47823@debbugs.gnu.org \
--cc=arne_bab@web.de \
--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 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).