Dear All,
I think there is a some architectural issues with the current
implementation of nsswitch or nsdispatch(3).
Let's assume you want to authenticate against an LDAP database. You will
install nss_ldap from port. You configure nss_ldap.conf with binddn and
its bindpw. Here comes the
Hello Mohacsi,
Dear All,
I think there is a some architectural issues with the current
implementation of nsswitch or nsdispatch(3).
Let's assume you want to authenticate against an LDAP database. You will
install nss_ldap from port. You configure nss_ldap.conf with binddn and
its bindpw.
In the last episode (May 24), Mohacsi Janos said:
I think there is a some architectural issues with the current
implementation of nsswitch or nsdispatch(3). Let's assume you want
to authenticate against an LDAP database. You will install nss_ldap
from port. You configure nss_ldap.conf
Hi Michael,
On Thu, 24 May 2007, Michael Bushkov wrote:
Hello Mohacsi,
Other solution(?) would be to limit binddn access to read-only (also
limiting access only few attributes in LDAP) then exposing the bindpw would
not create big problem. However maintenance of LDAP ACI-s could be
Hello!
I'm the SoC student who will work on Distributed Audit Daemon
project this summer. It was some discussion between me, my mentor
Bjoern Zeeb bz@ and Robert Watson rwatson@ about design of
this project. In this message I want to describe preliminary version
of design we're likely to have.
I was able to resolve this issue. Another sys-admin pointed out that my
boot0cfg had the disk setup in CHS apposed to LBA. See below:
|[EMAIL PROTECTED] root]# boot0cfg -v ad0
|# flag start chs type end chs offset size
|1 0x80 0: 1: 1 0xa5 1023:254:63
Comments inline...
Dag-Erling Smørgrav wrote:
Lawrence Stewart [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
Since you are writing kernel code, I assume you have KDB/DDB in your
kernel and know how to use it.
I don't know how to use them really. Thus
7 matches
Mail list logo
