9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Povolotsky <ap80@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server as FS
Date: Tue,  8 May 2001 08:30:12 +0000	[thread overview]
Message-ID: <9cvc7b$55v@nntpa.cb.lucent.com> (raw)
In-Reply-To: <E14vbls-000C0G-0B@finch-post-11.mail.demon.net>

Man pages do not show options "listen" and "noauth" for kfscmd - where it
came from ?
"Richard Miller" <miller@hamnavoe.demon.co.uk> wrote in message
news:E14vbls-000C0G-0B@finch-post-11.mail.demon.net...
> > I think.  It only works on cpu servers
> > (/dev/key has to be readable).
>
> True, for file service with authentication you do need to run it on a
> cpu server.
>
> But kfs on a terminal will also serve its filesystem to the network
> if you do 'disk/kfscmd listen'.  If you add 'disk/kfscmd noneattach',
> then other machines will be able to attach as user 'none'.
> If you add 'disk/kfscmd noauth', other machines will be able to attach
> as any user, but kfs will accept the remote user identity without
> attempting to authenticate.
>
> Clearly this is not at all secure; but it may be useful on a local
> network of trusted machines, with no outside connection -- for example,
> to "synchronise" your laptop with the fs on a standalone Plan 9 machine.
>
> -- Richard
>


  reply	other threads:[~2001-05-08  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04  8:53 Richard Miller
2001-05-08  8:30 ` Alexander Povolotsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08 13:22 rob pike
2001-05-04  1:49 Russ Cox
2001-05-04  1:23 matt

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='9cvc7b$55v@nntpa.cb.lucent.com' \
    --to=ap80@lucent.com \
    --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).