On Tue, 29 Dec 2009, Kenneth Holter wrote:
We're working on setting up Red Hat Directory Server (RHDS), and need to make
a decision about wether sudo information should be defined as sudo-objects in
the directory server, or if we should stick to /etc/sudoers. I've played
around with
Hi everyone,
389-directory is working with free-radius or it has any scheme for
freeradius
Bu mesaj ve onunla iletilen tum ekler gonderildigi kisi ya da kuruma ozel,
gizlilik yukumlulugu tasiyor olabilir. Bu mesaj, hicbir sekilde, herhangi bir
amac icin cogaltilamaz, yayinlanamaz ve
Prashanth Sundaram wrote:
I have two 389-ds servers with MMR via TLS and client hosts
authenticating via TLS. I see this error message in all client machines
in /var/log/messages. It seems nscd is failing at random intervals. Has
anyone seen this before?
Dec 29 10:35:35 dmc189 nscd:
HI All,
I am following the instruction on how to enable SSL via
http://www.directory.fedora.redhat.com/wiki/Howto:SSL
One of the step mentioned to create addRSA.ldif. What exactly does this
file do? and why it is necessary?
Thanks!
- David
--
389 users mailing list
389-us...@redhat.com
Not to digress too much off topic here, but I'm not sure about your comment
on using groups- we've organized privileges into entry's like this:
cn=reporting_admin_on_sas,ou=sudoers,ou=foo,dc=com
sudoHost: sasapp*.prod.foo.com
objectClass: sudoRole
objectClass: top
sudoCommand: /bin/su sas
On Tue, Dec 29, 2009 at 7:33 AM, Anne Cross across itasoftware com
wrote:
We're going to go with sudoers in ldap, not because I think it's
better, but because it's somewhat more secure. I think the layout
of how it's managed in ldap is much inferior (having to declare each
group
On Wed, 30 Dec 2009, Chun Tat David Chu wrote:
HI All,
I am following the instruction on how to enable SSL via
http://www.directory.fedora.redhat.com/wiki/Howto:SSL
One of the step mentioned to create addRSA.ldif. What exactly does this
file do? and why it is necessary?\
The file
