Re: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
- From: "Richard E. Silverman" <res@xxxxxxxx>
- Date: 22 Jun 2006 22:29:30 -0400
this is pretty much where the two outputs go different so I have a gut
feeling that this might be why ...
It's the proximate reason, yes. You are showing the key exchange rather
than user authentication which comes later, so this is not directly the
reason why you can't log in via Kerberos. However, this indicates that
the server does not think it can support Kerberos, so it would probably
not work for user authentication either.
any ideas how to go about fixing this ... making server1 to offer
gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g== as an option?
There are a number of reasons why it might not work (missing keytab,
mismatched key version numbers, etc.). You usually get better error
messages for Kerberos on the server side; run the server in debugging mode
and see what it says.
--
Richard Silverman
res@xxxxxxxx
.
- References:
- gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
- From: atari8472@xxxxxxxxx
- gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
- Prev by Date: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
- Next by Date: ssh configuration
- Previous by thread: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==
- Next by thread: ssh configuration
- Index(es):
Relevant Pages
|
|