s this
> the kdc ?) is used, so it sounds kadmind can not answer for all realms
> despite the second sentence.
>
> Why can't kadmind be use like krb5kdc with -r REALM1 and -r REALM2 ?
>
> Markus
>
>
> "Anthony Brock" <[EMAIL PROTECTED]> wrote in mes
kdc code. Which release do you use ?
>
> Markus
>
> "Anthony Brock" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Unfortunately I'm not necessarily familiar enough to know if I'm seeing
> > the
> > "correct" tic
er
> Sent: Monday, September 24, 2007 1:39 PM
> To: kerberos@mit.edu
> Subject: Re: Problems with kadmind, kpasswd and cross-realm
> authentication
>
>
> What do you see when you capture the traffic with wireshark on
> port 88 and
> 464 ? Do you see the correct kadmi
> -Original Message-
> Any ideas?
>
> The man page states that kadmind should be able to change
> passwords for any
> realms that have an associated kadmin/changepw@ and
> kadmin/admin@ principal. Is this still true? Or has
> support for this
> functionality been dropped? If not, what debug
> -Original Message-
> kpasswd doesn't work on the KDC. It only works for the initial realm even
> when the kpasswd command is issued on the KDC. That's why I'm a little
> baffled as to how to proceed. I've read the following in the kadmind man
> page:
>
< ... SNIP ...
>
> An excerpt of the
> -Original Message-
> Anthony Brock <[EMAIL PROTECTED]> wrote:
> > No, the entire network is on a single, private IP address range. In
> > fact, I'm trying these particular commands on the same host that
> > kadmind is running on. However, the behavior
> -Original Message-
> Anthony Brock <[EMAIL PROTECTED]> wrote:
> > I have created several cross-realm trusts on a test server. At this
> > point, nearly everything is working properly. However, users are
> > unable to change their passwords unless their
MIT Kerberos
administration runtime librarie
ii libkrb5-17-heimdal 0.7.2.dfsg.1-10 Libraries for Heimdal
Kerberos
ii libkrb531.6.dfsg.1-6 MIT Kerberos runtime
libraries
Any help will be greatly appreciated!
Tony
> -Original Message-
> Fr
I have created several cross-realm trusts on a test server. At this point,
nearly everything is working properly. However, users are unable to change
their passwords unless their account is in the initial domain. Users see the
following when attempting it from the initial domain:
# kpasswd
Passwor
che: FILE:/tmp/krb5cc_100
Default principal: [EMAIL PROTECTED]
Valid starting ExpiresService principal
09/18/02 09:52:29 09/18/02 19:52:29
[EMAIL PROTECTED]
09/18/02 09:52:36 09/18/02 19:52:29
[EMAIL PROTECTED]
abrock@web ~ 523 $
* END *
Anthony Brock
Director of Network
10 matches
Mail list logo
