9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] obsolete cryptographic algorithms
Date: Wed, 28 Sep 2022 08:41:54 +0200	[thread overview]
Message-ID: <CAFSF3XN0U7+-s9k38-NfJHpv-h+G5S4HEHP6rGCWy-a8CLCPfQ@mail.gmail.com> (raw)
In-Reply-To: <532502E979B5760FCA5D7CE49FB9CA4F@eigenstate.org>

git history is a shitty way to organise rarely used files.

On 9/28/22, ori@eigenstate.org <ori@eigenstate.org> wrote:
> Quoth Michael Forney <mforney@mforney.org>:
>>
>> 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?
>
> I think I'm happy enough to see them gone if we're certain that they're
> dead code. If it turns out that there's soemthing that needs them, we can
> always bring it back from history -- though I don't know what protocols
> force DSA or ElGamal.
>
>

  reply	other threads:[~2022-09-28  6:43 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 [this message]
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:
  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=CAFSF3XN0U7+-s9k38-NfJHpv-h+G5S4HEHP6rGCWy-a8CLCPfQ@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).