From: Chris McGee <sirnewton_01@yahoo.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Questions on the browser as a platform if plan 9 had gained marketshare
Date: Mon, 19 Sep 2016 13:25:34 -0400 [thread overview]
Message-ID: <92A3C379-3B7C-4EB6-9225-BCC5531BA585@yahoo.ca> (raw)
In-Reply-To: <CAK0pxsFS6MEeQi6QEANkX6FmQXaY76U+5Buybsr2K+yKUrkepQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
>
> > You just mount search engine, route planning tool, or even shopping site and echo commands into the ctl file.
>
> I hadn't thought of this - was more thinking on the user union mounting, say, google.com/bin into their bin directory and running a google operation. The concept of just echoing into a ctl file is really interesting from a security perspective.
Right, in this case there is no remote code execution. Web users run all kinds of code they are unaware of today. It's a major problem.
It also helps to create a certain uniformity and expectation of how services should work.
Mounting a bin directory from some remote servers is a potential vector for malicious code and requires all services to provide binaries for all platforms (arm, x86, riscv,...). Instead, serving the source code and mkfile allows for audit ability (what did I just run?) and support for their own platform. Plan 9 compilers were designed not just to produce optimal code but also for speed of compilation.
[-- Attachment #2: Type: text/html, Size: 1464 bytes --]
next prev parent reply other threads:[~2016-09-19 17:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 12:44 Marshall Conover
2016-09-19 17:25 ` Chris McGee [this message]
2016-09-19 20:55 ` Chris McGee
2016-09-20 6:16 ` David Pick
2016-09-20 17:42 ` Chris McGee
2016-09-22 22:49 ` michaelian ennis
2016-09-22 22:53 ` Chris McGee
2016-09-20 7:47 ` hiro
2016-09-20 8:09 ` hiro
-- strict thread matches above, loose matches on Subject: below --
2016-10-01 20:17 Marshall Conover
2016-10-01 20:21 ` Jules Merit
2016-09-20 16:48 Marshall Conover
2016-09-20 19:46 ` hiro
2016-09-19 22:00 Marshall Conover
2016-09-21 3:11 ` Chris McGee
2016-09-17 15:19 Marshall Conover
2016-09-17 16:23 ` Chris McGee
2016-09-17 17:04 ` hiro
2016-09-17 18:51 ` Jules Merit
2016-09-19 17:11 ` michaelian ennis
2016-10-01 15:03 ` James A. Robinson
2016-10-01 15:05 ` James A. Robinson
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=92A3C379-3B7C-4EB6-9225-BCC5531BA585@yahoo.ca \
--to=sirnewton_01@yahoo.ca \
--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).