From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] terminal level authentication
Date: Mon, 28 Mar 2005 17:20:26 +0200 [thread overview]
Message-ID: <bee6839596dc2ed8febb144f9dd18c57@voidness.de> (raw)
In-Reply-To: <200503281000.j2SA0HuT007469@pmxsrv.astec-power.com>
Hi Fernan,
> I recently put together a small plan 9 network.
>
> I noticed that just about anyone can access the terminal,
> because it does not ask for authentication when I log in.
> It will only ask for my password when access the cpu server
> or import from the servers.
>
> I am not sure if it was a mistake on my part that I might
> have overlooked a step. If so can you pls tell me which steps?
This is right. The resources on a standalone terminal aren't
protected from the user (=hostowner) by password (or any other
method of authentication)
(We had a discussion about this regarding notebooks some weeks before
on the 9fans list.)
Terminals are meant to boot from a fileserver and to not have the
operating system installed on local disks. You need to authenticate
with password (perhaps via sectore key) when you boot a terminal from
fileserver.
If you do have a local installed Plan 9 system (e.g. on notebooks)
you perhaps will only want to use that for temporary use in situations
when you are unconnected to any Plan 9 authdom you have an account
for.
This all is intended by design. These ideas are described in
http://plan9.bell-labs.com/sys/doc/9.ps and
http://plan9.bell-labs.com/sys/doc/auth.ps describes the
authentication and security infrastructures.
> Assuming I did not make a mistake during the installation.
> If a user decided to make use of the terminals disks
> to store data, what protects these data from other users? Ofcourse
> this would be irrelevant if the terminals where made of diskless
> machines which relies on the fileserver to provide the disk space.
>
> As I understand it, Just installing the distro form the bell labs site.
> The reulting machine is a standalone terminal.
yes.
> If I decide to follow the configuring the cpu server in the wiki,
> this will give me a cpu server.
yes.
Heiko
prev parent reply other threads:[~2005-03-28 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 10:04 FernanBolando
2005-03-28 15:08 ` Russ Cox
2005-03-28 15:20 ` Heiko Dudzus [this message]
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=bee6839596dc2ed8febb144f9dd18c57@voidness.de \
--to=heiko.dudzus@gmx.de \
--cc=9fans@cse.psu.edu \
/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).