9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] question about #include_next directive
Date: Fri,  3 Aug 2018 17:19:36 +0200	[thread overview]
Message-ID: <6A9EF44411819E268CC3A6175C6F2C10@felloff.net> (raw)
In-Reply-To: CAFMepc=tjm3V4VPYzsAWTaHGRcSi3b0C5Z44W8J9oFbhrX5apw@mail.gmail.com

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



             reply	other threads:[~2018-08-03 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 15:19 cinap_lenrek [this message]
2018-08-03 18:35 ` Kyohei Kadota
2018-08-03 18:54   ` Lyndon Nerenberg
2018-08-03 19:10   ` Dave MacFarlane
2018-08-03 22:55     ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2018-08-03 14:35 Kyohei Kadota

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=6A9EF44411819E268CC3A6175C6F2C10@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9fans@9fans.net \
    /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).