On Tuesday, April 11, 2006 08:40:10 PM +0200 Sensei [EMAIL PROTECTED]
wrote:
Good. One thing I noticed on many clients here is that an ntpdate at
boot solution is not good, since it can produce large time drifts if
you don't reboot the clients often. A cron job was my solution.
Note that
On 2006-04-11 01:37:06 +0200, Quinten [EMAIL PROTECTED] said:
Naive question... can you kinit the NOT_DEFAULT_REALM?
Buck: To clear out my misconceptions on the definition of
authentication, I meant logging on with SSH from another machine. I am
indeed able to kinit succesfully as both
Sensei schreef:
On 2006-04-04 17:22:04 +0200, Quinten [EMAIL PROTECTED] said:
Sensei schreef:
On 2006-03-30 01:21:04 +0200, Quinten [EMAIL PROTECTED] said:
Our environment is currently using 2 AD/realms. I am trying to set
up a RHEL3 host to authenticate users from both realms. If the
Sensei schreef:
On 2006-03-30 01:21:04 +0200, Quinten [EMAIL PROTECTED] said:
Our environment is currently using 2 AD/realms. I am trying to set
up a RHEL3 host to authenticate users from both realms. If the
default_realm in /etc/krb5.conf is set to one realm, the users in the
other
Hello,
Our environment is currently using 2 AD/realms. I am trying to set up
a RHEL3 host to authenticate users from both realms. If the
default_realm in /etc/krb5.conf is set to one realm, the users in the
other realm cannot authenticate and vice versa. So there is no issue on
any
On 2006-03-30 01:21:04 +0200, Quinten [EMAIL PROTECTED] said:
Our environment is currently using 2 AD/realms. I am trying to set up
a RHEL3 host to authenticate users from both realms. If the
default_realm in /etc/krb5.conf is set to one realm, the users in the
other realm cannot
