From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <6A9EF44411819E268CC3A6175C6F2C10@felloff.net> In-Reply-To: <6A9EF44411819E268CC3A6175C6F2C10@felloff.net> From: Kyohei Kadota Date: Sat, 4 Aug 2018 03:35:38 +0900 Message-ID: To: 9fans@9fans.net Content-Type: multipart/alternative; boundary="0000000000005eee4305728c321c" Subject: Re: [9fans] question about #include_next directive Topicbox-Message-UUID: d9d5c364-ead9-11e9-9d60-3106f5b1d025 --0000000000005eee4305728c321c Content-Type: text/plain; charset="UTF-8" Thanks cinap. I know Plan 9's devtls is more useful than Unix's libraries, but finally want to use git and github.com on Plan 9. My team works frequently with git. Git-wrapper can clone but it can't merge, push, and so on. And I started to port LibreSSL because official git links some libraries such as libexpat, libcurl, and openssl. 2018-08-04 0:22 : > what are you intending to use libressl for in native plan9? > plan9 already has a crypto library (libsec) which is a fraction of the > size of openssl and works quite well. i'v been using it to implement > many crypto protocols to talk to the outside world. > > for tls, plan9 uses devtls which allows you to wrap any file descriptor > to make it a encrypted channel and then you get a filedescriptor back > that you can pass arround, so the programs communicating actually dont > even need to know the secret session keys. so adding tls support to > programs is very trivial in plan9. one function call basically to wrap > the fd. while in unix programs that want encryption have to change all > ther read and wirte calls to use special libssl functions. > > also, plan9 has factotum to hold and work on secret keys. you can use > factotum todo the public key operations like signing, encryption and > decryption using the key for you so keys never have to leave factotum. > > even if you port programs from unix, it might be worth taking a step > back and learn how plan9 does crypto, which is quite advanced compared > to traditional unix. > > -- > cinap > > --0000000000005eee4305728c321c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks cinap.

I know Pl= an 9's devtls is more useful than Unix's libraries, but finally wan= t to use git and github.com on Plan 9.
My team works frequently with git.

Git-wra= pper can clone but it can't merge, push, and so on.
And I sta= rted to port LibreSSL because official git links some libraries such as lib= expat, libcurl, and openssl.

2018-08-04 0:22 <cinap_lenrek@felloff.net>:
what are you = intending to use libressl for in native plan9?
plan9 already has a crypto library (libsec) which is a fraction of the
size of openssl and works quite well. i'v been using it to implement many crypto protocols to talk to the outside world.

for tls, plan9 uses devtls which allows you to wrap any file descriptor
to make it a encrypted channel and then you get a filedescriptor back
that you can pass arround, so the programs communicating actually dont
even need to know the secret session keys. so adding tls support to
programs is very trivial in plan9. one function call basically to wrap
the fd. while in unix programs that want encryption have to change all
ther read and wirte calls to use special libssl functions.

also, plan9 has factotum to hold and work on secret keys. you can use
factotum todo the public key operations like signing, encryption and
decryption using the key for you so keys never have to leave factotum.

even if you port programs from unix, it might be worth taking a step
back and learn how plan9 does crypto, which is quite advanced compared
to traditional unix.

--
cinap

--0000000000005eee4305728c321c--