From: wiLL <wol...@sk...> - 2000-08-16 07:12:53
|
I've been working with binding usernames with their corresponding paswd in the LDAP tree, but this is just when a user would access a particular http directory ... I just realized I needed also to restrict ldap urls from being accessed by anyone .. Does anybody knows how this one goes? will ------------------------------------- wiLL S. Olivete Jr. wol...@sk... pgp key id : 0x2D85D7BF office voice: 63.74.443.5657 mobile: 0917.972.6384 pager: ec 963576 |
From: Mark W. <mew...@un...> - 2000-08-16 13:17:07
|
Nobody (at least that I know of) supports authenticated operations via LDAP URLs. Just eliminate anonymous searches to your server and that will prevent LDAP URLs. Mark On Wed, 16 Aug 2000, wiLL wrote: > > I've been working with binding usernames with their corresponding paswd in > the LDAP tree, but this is just when a user would access a particular http > directory ... I just realized I needed also to restrict ldap urls from > being accessed by anyone .. Does anybody knows how this one goes? > > will > > ------------------------------------- > wiLL S. Olivete Jr. > wol...@sk... > pgp key id : 0x2D85D7BF > office voice: 63.74.443.5657 > mobile: 0917.972.6384 > pager: ec 963576 > > |
From: Jim H. <ha...@us...> - 2000-08-16 15:11:14
|
LDAP URLS basically just say "use the LDAP protocol to get some information". You need to deal with the general issue of LDAP access to your server. For example, we block access to that port at our router, except for holes opened to 2 specific ports. Your server may have some type of control available also. --Jim Harle On Wed, 16 Aug 2000, Mark Wilcox wrote: > Nobody (at least that I know of) supports authenticated operations via > LDAP URLs. Just eliminate anonymous searches to your server and that will > prevent LDAP URLs. > > Mark > > On Wed, 16 Aug 2000, wiLL wrote: > > > > > I've been working with binding usernames with their corresponding paswd in > > the LDAP tree, but this is just when a user would access a particular http > > directory ... I just realized I needed also to restrict ldap urls from > > being accessed by anyone .. Does anybody knows how this one goes? > > > > will > > > > ------------------------------------- > > wiLL S. Olivete Jr. > > wol...@sk... > > pgp key id : 0x2D85D7BF > > office voice: 63.74.443.5657 > > mobile: 0917.972.6384 > > pager: ec 963576 > > > > > > > |
From: wiLL <wol...@sk...> - 2000-08-23 10:15:09
|
I tried to eliminate anonymous searches on my server , but it doesnt seem to like it .. the slapd daemon wont run if i put the ff. on my slapd.conf file, there arent any error messages though , is this correct ?... ------------ : : database ldbm suffix "o=mycom, c=PH" rootdn "uid=Manager, o=mycom, c=PH" # database directory # this directory MUST exist prior to running slapd AND # should only be accessable by the slapd/tools Mode 700 recommended. directory /usr/local/var/openldap-ldbm access to * by self write by anonymous none : : -------------------------------- At 11:09 PM 8/16/00 , Jim Harle wrote: >LDAP URLS basically just say "use the LDAP protocol to get some >information". You need to deal with the general issue of LDAP access to >your server. For example, we block access to that port at our router, >except for holes opened to 2 specific ports. Your server may have some >type of control available also. > --Jim Harle > > >On Wed, 16 Aug 2000, Mark Wilcox wrote: > >> Nobody (at least that I know of) supports authenticated operations via >> LDAP URLs. Just eliminate anonymous searches to your server and that will >> prevent LDAP URLs. >> >> Mark >> >> On Wed, 16 Aug 2000, wiLL wrote: >> >> > >> > I've been working with binding usernames with their corresponding paswd in >> > the LDAP tree, but this is just when a user would access a particular http >> > directory ... I just realized I needed also to restrict ldap urls from >> > being accessed by anyone .. Does anybody knows how this one goes? >> > >> > will >> > >> > ------------------------------------- >> > wiLL S. Olivete Jr. >> > wol...@sk... >> > pgp key id : 0x2D85D7BF >> > office voice: 63.74.443.5657 >> > mobile: 0917.972.6384 >> > pager: ec 963576 >> > >> > >> >> >> > ------------------------------------- wiLL S. Olivete Jr. wol...@sk... pgp key id : 0x2D85D7BF office voice: 63.74.443.5657 mobile: 0917.972.6384 pager: ec 963576 |
From: Mark W. <mew...@un...> - 2000-08-23 13:32:05
|
Kurt Z might pop in, but you'll likey have better luck with this question by asking on the openldap-server list. Mark On Wed, 23 Aug 2000, wiLL wrote: > I tried to eliminate anonymous searches on my server , but it doesnt seem > to like it .. > the slapd daemon wont run if i put the ff. on my slapd.conf file, there > arent any error messages though , is this correct ?... > > ------------ > : > : > database ldbm > suffix "o=mycom, c=PH" > rootdn "uid=Manager, o=mycom, c=PH" > # database directory > # this directory MUST exist prior to running slapd AND > # should only be accessable by the slapd/tools Mode 700 recommended. > directory /usr/local/var/openldap-ldbm > access to * > by self write > by anonymous none > > : > : > -------------------------------- > > > > At 11:09 PM 8/16/00 , Jim Harle wrote: > >LDAP URLS basically just say "use the LDAP protocol to get some > >information". You need to deal with the general issue of LDAP access to > >your server. For example, we block access to that port at our router, > >except for holes opened to 2 specific ports. Your server may have some > >type of control available also. > > --Jim Harle > > > > > >On Wed, 16 Aug 2000, Mark Wilcox wrote: > > > >> Nobody (at least that I know of) supports authenticated operations via > >> LDAP URLs. Just eliminate anonymous searches to your server and that will > >> prevent LDAP URLs. > >> > >> Mark > >> > >> On Wed, 16 Aug 2000, wiLL wrote: > >> > >> > > >> > I've been working with binding usernames with their corresponding > paswd in > >> > the LDAP tree, but this is just when a user would access a particular > http > >> > directory ... I just realized I needed also to restrict ldap urls from > >> > being accessed by anyone .. Does anybody knows how this one goes? > >> > > >> > will > >> > > >> > ------------------------------------- > >> > wiLL S. Olivete Jr. > >> > wol...@sk... > >> > pgp key id : 0x2D85D7BF > >> > office voice: 63.74.443.5657 > >> > mobile: 0917.972.6384 > >> > pager: ec 963576 > >> > > >> > > >> > >> > >> > > > > ------------------------------------- > wiLL S. Olivete Jr. > wol...@sk... > pgp key id : 0x2D85D7BF > office voice: 63.74.443.5657 > mobile: 0917.972.6384 > pager: ec 963576 > > |
From: Kurt D. Z. <Ku...@Op...> - 2000-08-23 13:58:06
|
At 08:25 AM 8/23/00 -0500, Mark Wilcox wrote: >Kurt Z might pop in, but you'll likey have better luck with this question >by asking on the openldap-server list. I'll pop in just long enough to say: http://www.openldap.org/lists/ Please redirect questions to the most appropriate list. For OpenLDAP software questions, that's <ope...@op...>. You must be subscribed to post. Kurt |