Date: Fri, 30 Jan 1998 10:28:40 -0500 (EST) From: Thomas David Rivers <rivers@dignus.com> To: mike@smith.net.au, tlambert@primenet.com Cc: capriotti0@hotmail.com, capriotti@geocities.com, hackers@FreeBSD.ORG, joe.shevland@horizonti.com Subject: Re: WebAdmin Message-ID: <199801301528.KAA29091@lakes.dignus.com>
next in thread | raw e-mail | index | archive | help
Well - just a heads' up on the LDAP issue. Computer Reseller News (www.crn.com) just published a lead article indicating LDAP is soon to be dead... People are finding it to be too ill defined producing too much incompatibility. Based solely on that article, since that's all I know - I'd suggest staying away from LDAP until a presumed newer definition materializes. - Dave Rivers - > > I've been waiting for people to actually move this discussion to the > -config mailing list, which is where it belongs. I've also avoided > weighing in because I haven't heard anything new yet. > > > This would all be a lot easier if all FreeBSD configuration information > > went to one place, and was accessed via one set of methods. Perhaps > > the LDAP methods, which are freely downloadable from the NetScape > > developer resources page at www.netscape.com? > > I'm not sure if I like these yet. > > > The massive number of FreeBSD databases need not change for this to > > work. FreeBSD could keep its fear of change and its proliferation > > of hundreds of incompatible text file and database formats, if it > > wanted to. You can write any LDAP back end you want to, including > > one that would allow you register multiple databases to manage > > various parts of the LDAP tree. > > Yes. Funnily enough, I have been looking at making the 'juliet' tool > work as a backend for the umich SLAPD LDAP daemon. > > The real gotcha with this is security; SLAPD's security is relatively > poor. > > Oh, and getting people to accept DNs, which aren't the nicest things to > read or write. > > > Finally, for boot and local usage, you would probably want to implement > > a native access to the LDAP methods. This would let you directly > > access the database data, instead of requiring that you get your net > > up before you can set up your net (catch 22). > > It wouldn't be hard to use a unix-domain socket for this. Start the > LDAP server early enough and you're in business. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801301528.KAA29091>