9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave MacFarlane <driusan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] question about #include_next directive
Date: Fri,  3 Aug 2018 15:10:23 -0400	[thread overview]
Message-ID: <CAG2UyHrjxGs=G=Bz0bQ6csQoEYUG=RvvjGiLsfG68tedAX+ySg@mail.gmail.com> (raw)
In-Reply-To: <CAFMepcnqfptMSf3ak9f=qJ-hWH72E4qD_gOP5WCX0mR7Ux60gw@mail.gmail.com>

How advanced is your git usage? If you're only doing simple merges and pushes
dgit (https://github.com/driusan/dgit) is approaching useful since
someone taught
me how to throw the official git test suite at it.

I definitely wouldn't recommend it as a daily driver, but if you only
want to push a
couple things here and there, don't rebase, and have a fairly linear
history it might
work for you.

- Dave

On Fri, Aug 3, 2018 at 2:35 PM, Kyohei Kadota <lufia@lufia.org> wrote:
> 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 <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
>>
>



--
- Dave



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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 15:19 cinap_lenrek
2018-08-03 18:35 ` Kyohei Kadota
2018-08-03 18:54   ` Lyndon Nerenberg
2018-08-03 19:10   ` Dave MacFarlane [this message]
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='CAG2UyHrjxGs=G=Bz0bQ6csQoEYUG=RvvjGiLsfG68tedAX+ySg@mail.gmail.com' \
    --to=driusan@gmail.com \
    --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).