9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sml <sml@firstpost.pub>
To: 9front@9front.org
Subject: [9front] obsolete cryptographic algorithms
Date: Sat, 4 Jun 2022 09:13:06 +0200	[thread overview]
Message-ID: <B7BDF2AE-D1D7-4716-B76C-91A8FEF6C1FC@firstpost.pub> (raw)

Hello everyone, 

I am currently trying to understand the implementation of factotum and I noticed that /sys/src/libsec contains some obsolete cryptographic algorithms like sha-1, md4, md5, dsa and des. 

In section of the fqa the manual change from p9sk1 to dp9ik is described and since then, as far as I understand, it is also the new standard where des has been replaced by aes. 

In the list I keep reading about different cleanups, which I greatly appreciate and I'm wondering whether the deprecated crypto algorithms and protocols can be cleaned out as well, or if there is a specific reason to hold on to them. I think if you use very weak crypto, you can do without it directly.

Many thanks in advance for your responses!

Best regards, 

             reply	other threads:[~2022-06-04  7:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  7:13 sml [this message]
2022-06-04 14:47 ` ori
2022-06-04 15:26   ` mkf9
2022-06-04 15:32     ` ori
2022-06-04 15:36       ` ori
2022-06-04 16:07         ` Stanley Lieber
2022-06-04 16:12           ` ori
2022-09-27 20:10   ` Michael Forney
2022-09-27 20:11     ` hiro
2022-09-27 20:31       ` Michael Forney
2022-09-27 21:40         ` hiro
2022-09-27 22:26     ` ori
2022-09-28  6:41       ` hiro
2022-09-29  5:01         ` ori
2022-09-29  6:17           ` unobe
2022-09-29  6:30             ` unobe
2022-09-29  8:53           ` hiro
2022-10-02 18:23     ` [9front] " magma698hfsp273p9f

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:

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

  git send-email \
    --in-reply-to=B7BDF2AE-D1D7-4716-B76C-91A8FEF6C1FC@firstpost.pub \
    --to=sml@firstpost.pub \
    --cc=9front@9front.org \


* 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.
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 NNTP newsgroup(s).