9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] u9fs authentication via auth server?
Date: Mon, 24 Jun 2002 15:30:56 +0200	[thread overview]
Message-ID: <200206241330.g5ODUuj20901@zamenhof.cs.utwente.nl> (raw)

Would it make sense to let u9fs use the (an) auth server to
authenticate, in the same way as a 'normal' (fake) worm fs does?
Such that we no longer need to know in advance from which plan 9
machines we allow access (as currently is the case, with .rhosts etc.?)
(we would still need on the unix side something to allow unix users to
 enable/disable access from plan 9, but that could be per unix user
 a(n) (number of) entrie(s) of the form user@plan9auth.dom)
Hmmm... what would it take to add something like this?

Looking at the u9fs sources I found a file auth9p1.c that is
by default not compiled. When I tried to compile (solaris 2.8)
I got compiler errors. What should that file do? (Use a 'remote'
auth server, or??)  Should it compile 'as is', or is it work
in progress?

Background:
This weekend I wanted to use my home machine to grab a file from
a unix machine in the office on which I have u9fs running,
but realized that my home machine's name is not in the .rhosts
file on the unix machine, and realized that it is not nice to really
have to add individual plan 9 machine names to allow access...


Just some thoughts,
Axel.




                 reply	other threads:[~2002-06-24 13:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200206241330.g5ODUuj20901@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).