[31859] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Wrong principal in request

daemon@ATHENA.MIT.EDU (Jeff Blaine)
Mon Jan 4 22:50:03 2010

Message-ID: <4B42B547.9040000@kickflop.net>
Date: Mon, 04 Jan 2010 22:43:03 -0500
From: Jeff Blaine <jblaine@kickflop.net>
MIME-Version: 1.0
To: Russ Allbery <rra@stanford.edu>
In-Reply-To: <87eim5z5ry.fsf@windlord.stanford.edu>
Content-Type: multipart/mixed; boundary="------------090301000403070301070501"
Cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu

This is a multi-part message in MIME format.
--------------090301000403070301070501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/4/2010 8:42 PM, Russ Allbery wrote:
> Jeff Blaine<jblaine@kickflop.net>  writes:
>
>> I happened to notice this (note the missing realm) after a
>> failed GSSAPI attempt to the SSH server (mega):
>
>> [root@mega ~]# klist
>> Ticket cache: FILE:/tmp/krb5cc_0
>> Default principal: jblaine@FOO
>
>> Valid starting     Expires            Service principal
>> 01/04/10 16:14:51  01/11/10 16:14:51  krbtgt/FOO@FOO
>>           renew until 01/18/10 16:14:51
>> 01/04/10 16:15:08  01/11/10 16:14:51  host/mega@
>>           renew until 01/18/10 16:14:51
>
> Ah, that means that the client doesn't know what the local realm is and is
> therefore trying to ask the server via referrals, but the server isn't
> answering that question.
>
>> I updated /etc/krb5.conf to include
>
>>       [domain_realm]
>>           mega = FOO
>
>> And all is well when connecting from mega to mega with OpenSSH
>> and GSSAPI options.
>
>> All is well, too, when connecting from sol10 SPARC stock SSH
>> to mega using GSSAPI options.
>
>> PuTTY-GSSAPI as the client still gives me the same error :(
>
> Did you update the Windows equivalent (krb5.ini, I think)?

I hadn't, but duplicated krb5.conf to C:\WINDOWS\krb5.ini to
replace the old one there (which worked fine for getting into
the Solaris 10 box via PuTTY + GSSAPI).

Same old same old.


OpenSSH sshd on mega reports:
...
mega sshd[3287]: debug1: userauth-request for user jblaine service 
ssh-connection method gssapi-with-mic
mega sshd[3287]: debug1: attempt 1 failures 1
mega sshd[3286]: debug1: PAM: setting PAM_RHOST to "192.168.1.4"
mega sshd[3286]: debug1: PAM: setting PAM_TTY to "ssh"
mega sshd[3287]: Postponed gssapi-with-mic for jblaine from 192.168.1.4 
port 50081 ssh2
mega sshd[3286]: debug1: Unspecified GSS failure.  Minor code may 
provide more information\nWrong principal in request\n
mega sshd[3286]: debug1: Got no client credentials
...

And the KDC reports:
...
AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.4: ISSUE: authtime 
1262662114, etypes {rep=18 tkt=18 ses=18}, jblaine@FOO for krbtgt/FOO@FOO
TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.4: ISSUE: authtime 
1262662114, etypes {rep=18 tkt=18 ses=18}, jblaine@FOO for 
host/192.168.1.6@FOO
TGS_REQ (1 etypes {18}) 192.168.1.4: ISSUE: authtime 1262662114, etypes 
{rep=18 tkt=18 ses=18}, jblaine@FOO for krbtgt/FOO@FOO

After the failed GSSAPI attempt, KfW looks like the attached
image.

--------------090301000403070301070501
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

--------------090301000403070301070501--

home help back first fref pref prev next nref lref last post