9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [Patch] APE changes (2019 Lufia patches)
Date: Fri, 26 Feb 2021 11:28:35 +0100	[thread overview]
Message-ID: <F8FB8C3F2E63856128599BD4704412F7@felloff.net> (raw)
In-Reply-To: <AB16C1EC181190E81B4CD57745C390A0@eigenstate.org>

Bringing back in libressl/openssl is a bad idea imho.
(note, we used to have it in the base system for mercurial)

These are unmaintainable monsters that take forever to compile
and have so much code churn that we cannot keep up with
constantly updating it.

We can use libsec from ape programs and it supports the
kernels tls device. it imlements all the modern ciphers
and tls support you need with a fraction of the codesize.
And libsec *is* maintained and in active use so receives
testing and porting/arch specific support (compiler work,
optimized assembly versions).

This was done for example for the python hash module to
use libsec instead of the openssl monster.

Theres also not really a reason for git to implement its
own dns, tls and https and ssh cients. All this is solved
i plan9 using webfs and ssh. If git calls curl, you can
probaly just write a wrapper script around it to use the
native plan9 infrastructure.

Dont try to emulate the broken way unix does networking
onto plan9. It is a waste of time. If you must, attempt
a proper port and *question* the dependencies that it
clams to be needing.

--
cinap

  reply	other threads:[~2021-02-26 10:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  2:48 bsdsm
2021-02-22  4:14 ` ori
2021-02-22  5:20   ` Jens Staal
2021-02-25  2:15 ` ori
2021-02-25  2:21   ` ori
2021-02-25 16:37     ` Aaron
2021-02-25 18:06       ` ori
2021-02-26 10:28         ` cinap_lenrek [this message]
2021-02-26 15:38           ` Lucas Francesco
2021-02-26 19:23 ` [9front] " bsdsm
2021-03-01  3:41   ` ori
2021-03-15  3:20   ` ori
2021-03-15  3:36   ` ori

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=F8FB8C3F2E63856128599BD4704412F7@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --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).