From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] obsolete cryptographic algorithms
Date: Thu, 29 Sep 2022 10:53:22 +0200 [thread overview]
Message-ID: <CAFSF3XP6ZGbiPzTUktBHaSHq60jZ7c5hp77N_73QXG7WxR+5xQ@mail.gmail.com> (raw)
In-Reply-To: <E94D4F9308F64B0EF891D8AE3EE69C7D@eigenstate.org>
> the belief here is that they're never used.
that's the thing about old protocols, it doesn't matter whether you
want them not to be used, some shitty gear might come with them
anyway.
what we try to provide here is called interoperability.
unlike linux, programs are limited to safer algorithms by default, so
it looks unused.
the balance to make is between maintainability and interoperability.
removing something is more work than not removing something.
next prev parent reply other threads:[~2022-09-29 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 7:13 sml
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 [this message]
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:
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=CAFSF3XP6ZGbiPzTUktBHaSHq60jZ7c5hp77N_73QXG7WxR+5xQ@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.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.
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).