[EMAIL PROTECTED] writes:
> Yup, it's at http://www.umich.edu/~dirsvcs/ldap/doc/guides/slapd/
Thanks. I don't know how I overlooked that.
I noticed in the README for libpam-ldap that you need to use some
secure socket mechanism if you really want an ldap setup to be secure.
Is there a doc somew
On Tue, Jun 15, 1999 at 12:09:20AM -0500, Rob Browning wrote:
> [EMAIL PROTECTED] writes:
>
> > Yea, this one stumped me for quite a while to. From section 5.3 of
> > the Slapd administrators guide: NOTE: The DN pattern specified
> > should be "normalized", meaning that there should be no extra
>
[EMAIL PROTECTED] writes:
> Yea, this one stumped me for quite a while to. From section 5.3 of
> the Slapd administrators guide: NOTE: The DN pattern specified
> should be "normalized", meaning that there should be no extra
> spaces, and commas should be used to separate components. An example
> n
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> You use the same technique as ethernet basically, both add and check
> if their was only one added (using a search on the ID they added)
> then remove and retry a new id after a delay.
Oh, right, of course.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E8
On Mon, Jun 14, 1999 at 12:18:05PM -0500, Rob Browning wrote:
>
> When I installed openldapd, it set up the admin user with a password,
> and in /etc/openldapd/slapd.conf I can see that that user's allowed to
> do anything:
>
> access to * by dn="cn=admin, ou=People, dc=localnet" write
>
Yea,
On 14 Jun 1999, Rob Browning wrote:
> Jason Gunthorpe <[EMAIL PROTECTED]> writes:
>
> > You don't really need this, just a simple detect/backoff algorithm will do
> > OK for determining the UIDs
>
> Could you elaborate? If you have at least two machines, I can't see
> how you don't have to hav
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> You don't really need this, just a simple detect/backoff algorithm will do
> OK for determining the UIDs
Could you elaborate? If you have at least two machines, I can't see
how you don't have to have a shared locking mechanism to make sure
they don't
On 14 Jun 1999, Rob Browning wrote:
> So my-ldap-adduser should look something like this:
>
> 1) acquire a global (across all the involved machines) lock (or just
> presume that only one machine will ever be used to add users and
> acquire a local lock). [1]
You don't really need th
Sergey V Kovalyov <[EMAIL PROTECTED]> writes:
> It is a package in potato.
Ahh. Though I imagine that this doesn't really help in the ldap case.
When using ldap, you can't use adduser if you really want ldap to be
serving a number of machines. You need to have some script that adds
entries to t
9 matches
Mail list logo
