9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Cyber Fonic <cyberfonic@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 security
Date: Tue, 20 Aug 2019 23:13:34 +1000	[thread overview]
Message-ID: <CALj3Nd0nauMxLiUpioOB=7+j_Jt_u0Sn+_WTfBC=fzyHwBogAw@mail.gmail.com> (raw)
In-Reply-To: <1e801ae2-0d18-4df9-a9a7-ec6480b9b6aa@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

I don't think OpenBSD will run on an ESP-32.  That is part of the problem
with IoT, the nodes are made on the cheap and thus use the cheapest viable
network capable device.

On Tue, 20 Aug 2019 at 00:54, Ethan Gardener <eekee57@fastmail.fm> wrote:

> On Mon, Aug 19, 2019, at 12:53 PM, Cyber Fonic wrote:
> >
> > It has been said : "The 'S' in IoT stands for security". If Plan9 can
> address that deficiency of the current state of the art for IoT devices,
> then it would be a worthwhile exercise.
>
> Plan 9 may have a decent security model, but it's never been audited.
> Auditing a codebase, even one as small as Plan 9's, is a lot of work.  Are
> you willing to make a start on it?
>
> If you want something free and already audited, with more security
> features, (but perhaps not quite the same convenience,) look into OpenBSD.
>
> --
> I love that *Open*BSD is so *security*-focused!
>
>

[-- Attachment #2: Type: text/html, Size: 1243 bytes --]

  reply	other threads:[~2019-08-20 13:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  6:37 [9fans] Plan 9 C compiler for Xtensa CPUs Cyber Fonic
2019-07-26 10:02 ` Rodrigo G. López
2019-07-26 10:30 ` Charles Forsyth
2019-07-26 12:04   ` Rodrigo G. López
2019-07-26 12:12   ` Cyber Fonic
2019-07-26 15:23   ` Charles Forsyth
2019-07-27  9:16     ` Anthony Martin
2019-07-27 11:10       ` Richard Miller
2019-07-27 16:29         ` Anthony Martin
2019-08-07  0:22   ` Charles Forsyth
2019-08-07  8:07     ` Lucio De Re
2019-08-09 14:17   ` Bakul Shah
2019-08-09 14:50     ` Charles Forsyth
2019-08-09 15:50       ` Charles Forsyth
2019-08-09 21:34         ` Charles Forsyth
2019-08-09 21:48           ` Shane Morris
2019-08-09 22:51           ` Bakul Shah
2019-08-09 22:53           ` Skip Tavakkolian
2019-08-10  9:09             ` Cyber Fonic
2019-08-10  9:15               ` Shane Morris
2019-08-10 16:18               ` Charles Forsyth
2019-08-11 18:59                 ` Lyndon Nerenberg
2019-08-18 14:10                 ` Charles Forsyth
2019-08-18 14:28                   ` Richard Miller
2019-08-19 11:51                   ` Cyber Fonic
2019-08-19 14:52                     ` [9fans] Plan 9 security Ethan Gardener
2019-08-20 13:13                       ` Cyber Fonic [this message]
2019-08-20 13:28                         ` Don A. Bailey
2019-08-23 18:45                           ` Ethan Gardener
2019-08-23 19:41                             ` Don Bailey

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='CALj3Nd0nauMxLiUpioOB=7+j_Jt_u0Sn+_WTfBC=fzyHwBogAw@mail.gmail.com' \
    --to=cyberfonic@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).