From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] authentication by LDAP?
Date: Tue, 3 Jan 2006 15:20:46 +0100 [thread overview]
Message-ID: <9f3897940601030620i11c87dafyefd833dc2a83b310@mail.gmail.com> (raw)
In-Reply-To: <faaa980a2065101fa62467283fa420a1@quintile.net>
On 1/2/06, Steve Simon <steve@quintile.net> wrote:
>
> One of these flat files could be DNS info from LDAP in ndb(6) format
> which you could simply reference in /lib/ndb/local, e.g.
[...]
> This is all very neat but vapourware at present - sorry, If I do get
> around to such a thing I will announce it here.
It looks like it will be the first job in our 'Hack club' :D
IDEA:
On linux machine, every x hours, a cron job will check ldap database
for new/changed/deleted entries and translate them to format supported
by plan9 software (updating the fileserver's user database in the
process).
And I decided not to read RFC's nor libldap manual/code... python-ldap
or perl-ldap will be used, and since perl-ldap is written entirely in
Perl, it might be possible to set it working as native plan9
fileserver (If you call perl program native :) )
The only problem I have is:
* Is there a simple way to setup linux box as ndb/auth/fileserver and
so on for plan9?
* How can I configure some unix DHCP server to send fileserver/auth
info to plan9 (I tried with ISC DHCPd... for some reason I can't get
it working)
* OR set-up Plan9's dhcp server (dhcp info isn't going to change that
often as to use LDAP :P )
> -Steve
>
--
Paweł Lasek
"Once a hitokiri, always a hitokiri. This will never change" - Jine-Ei
http://plasek.jogger.pl [in polish]
http://plasek.wordpress.com [in polish too ;-) ]
next prev parent reply other threads:[~2006-01-03 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 22:32 Paweł Lasek
2006-01-02 12:35 ` Steve Simon
2006-01-03 1:12 ` erik quanstrom
2006-01-03 1:15 ` Russ Cox
2006-01-03 2:13 ` erik quanstrom
2006-01-03 2:34 ` Russ Cox
2006-01-03 2:53 ` erik quanstrom
2006-01-03 14:20 ` Paweł Lasek [this message]
2006-01-03 17:20 ` Dan Cross
2006-01-04 22:13 ` Paweł Lasek
2006-01-07 3:13 ` erik quanstrom
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=9f3897940601030620i11c87dafyefd833dc2a83b310@mail.gmail.com \
--to=pawel.lasek@gmail.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).