From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Factotum vs SASL
Date: Mon, 1 Dec 2014 09:00:46 +0200 [thread overview]
Message-ID: <873a3482d7cbc73496b64baa73c718a5@proxima.alt.za> (raw)
In-Reply-To: <547C0A85.9090906@gr13.net>
> The guy in front of the console should authenticate as a normal user
> and then only be allowed to access his own environment (no direct
> control over hw, etc).
The guy is not in front of the "console", he has physical and
therefore unrestricted access to all the resources in the terminal. A
CPU or file server is used to offer limited access to restricted
resources. The terminal user is meant not to have physical access to
such devices.
It's no use bucking against that paradigm, it is fundamental to Plan
9's design.
Lucio.
PS: An auth server is meant to be kept under lock and key, separate
from the open network. That does not normally happen, but it is
designed to be possible.
next prev parent reply other threads:[~2014-12-01 7:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 5:03 Enrico Weigelt, metux IT consult
2014-11-17 5:57 ` Lyndon Nerenberg
2014-11-17 6:29 ` lucio
2014-11-17 13:58 ` erik quanstrom
2014-11-17 14:14 ` lucio
2014-11-18 8:22 ` Skip Tavakkolian
2014-11-29 19:46 ` Enrico Weigelt, metux IT consult
2014-11-29 19:46 ` erik quanstrom
2014-11-29 21:20 ` Enrico Weigelt, metux IT consult
2014-11-29 21:23 ` erik quanstrom
2014-12-01 6:28 ` Enrico Weigelt, metux IT consult
2014-12-01 7:00 ` lucio [this message]
2014-12-01 10:38 ` tlaronde
2014-12-01 10:45 ` lucio
2014-12-02 4:00 ` Enrico Weigelt, metux IT consult
2014-12-02 4:08 ` erik quanstrom
2014-12-02 15:40 ` plannine
2014-12-02 16:33 ` Wes Kussmaul
2014-12-02 20:32 ` Skip Tavakkolian
2014-12-02 22:20 ` Enrico Weigelt, metux IT consult
2014-12-02 9:50 ` Richard Miller
2014-12-02 22:15 ` Enrico Weigelt, metux IT consult
2014-12-01 12:14 ` Stuart Morrow
2014-12-02 20:32 ` Skip Tavakkolian
2015-01-01 14:55 ` Teodoro Santoni
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=873a3482d7cbc73496b64baa73c718a5@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).