From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] SSH server
Date: Fri, 27 Nov 2009 16:24:51 +0200 [thread overview]
Message-ID: <418c4ae286cd3a840b34bbfeaf61cfdb@proxima.alt.za> (raw)
In-Reply-To: <3327f69dce9b47312a2241e1237c21cc@terzarima.net>
>>If it is, there's a depth of cleverness in the new Plan 9
>>security model that I had missed until now, namely the elimination of
>>the intermediate "superuser" step required by the Unix paradigm.
>
> indeed that's the point.
Too clever for my ageing brain :-) Of course, I knew the facility
existed, but I didn't associate it with the absence of "root" and the
elimination of setuid(). I think this type of subtle cleverness
should be documented more explicitly, I'm sure I'm not the only one to
overlook its ramifications. Like, as another example. the use of
groups in Plan 9, together with the group leader: nowhere are there
good examples that clarify how different these are from the Unix
model. And documenting these principles is not easy: you need to
understand them very well.
++L
next parent reply other threads:[~2009-11-27 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3327f69dce9b47312a2241e1237c21cc@terzarima.net>
2009-11-27 14:24 ` lucio [this message]
[not found] <<2bbd9d864595a511b56be74fdbc2731a@proxima.alt.za>
2009-11-30 1:18 ` erik quanstrom
[not found] <<6762cbd7bf173e42934a64dc83c8c058@proxima.alt.za>
2009-11-27 16:27 ` erik quanstrom
[not found] <<f1b2f4c5f8d6de82065fd8e1fbc3f4c0@hamnavoe.com>
2009-11-27 16:23 ` erik quanstrom
2009-11-27 17:29 ` lucio
[not found] <<7c1427995df1b87ae465a79ab9efda18@proxima.alt.za>
2009-11-27 15:18 ` erik quanstrom
2009-11-27 15:22 ` lucio
[not found] <<d647b5ee08eac1f29f7d9715c6356dbd@hamnavoe.com>
2009-11-27 14:52 ` erik quanstrom
2009-11-27 15:18 ` lucio
2009-11-27 15:21 ` Richard Miller
2009-11-27 15:24 ` lucio
2009-11-27 15:26 ` lucio
2009-11-27 4:18 lucio
2009-11-27 10:00 ` Richard Miller
2009-11-27 10:30 ` lucio
2009-11-27 14:16 ` Charles Forsyth
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=418c4ae286cd3a840b34bbfeaf61cfdb@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).