From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <6A9EF44411819E268CC3A6175C6F2C10@felloff.net>
Date: Fri,  3 Aug 2018 17:19:36 +0200
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
In-Reply-To: CAFMepc=tjm3V4VPYzsAWTaHGRcSi3b0C5Z44W8J9oFbhrX5apw@mail.gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] question about #include_next directive
Topicbox-Message-UUID: d9ca9da4-ead9-11e9-9d60-3106f5b1d025

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