Subject: [9front] Re: obsolete cryptographic algorithms
Date: Sun, 02 Oct 2022 18:23:26 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <3SV1D3BDX9GTI.2KFKQ4XBWIE2D@mforney.org> (Michael Forney's message of "Tue, 27 Sep 2022 13:10:08 -0700")
Michael Forney <firstname.lastname@example.org> writes:
> email@example.com wrote:
>> Protocols still use them.
> What about the ones that aren't used by anything in 9front? I was
> poking around libsec a while back and noticed that dsa and elgamal
> are completely unused.
> Any reason to keep them around? Is there external plan9 software
> out there that uses dsa or elgamal from libsec?
THERE IS REALLY NO SUCH THING AS AN OBSOLETE CRYPTOGRAPHIC ALOGRITHM.
I set that in caps because it demands emphasis. There are many old
archives, network devices, and other systems which may (and do) employ
older cryptographic technologies. Removing support from 9front would
remove the ability to read/interact with legacy systems. I encountered
this problem when some "obsolete" ciphers were removed from the Linux
cryptoapi. I ended up having to re-implement one of them as a command-
line utility in C, just so I could access data written using a prior
version. As long as old machines, old software, and old data exists,
there is really no such thing as an obsolete cryptographic alogrithm.
prev parent reply other threads:[~2022-10-02 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 7:13 [9front] " 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
2022-10-02 18:23 ` magma698hfsp273p9f [this message]
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 \
* 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).