Bug#402844: libsasl2-modules-gssapi-mit: sasl-sample-client/sasl-sample-server authentication fails with GSSAPI mechanism

[Michael Richters]

On Thu, Dec 14, 2006 at 08:23:58AM +0200, Fabian Fagerholm wrote:
> Could you please try the following:
> 
> On the client:
> $ kinit
> $ sasl-sample-client -m gssapi -n geomancer.nutwerk.org
> 
> On the server:
> $ sasl-sample-server
> 
> Then manually copy and paste the server output (the whole line, starting
> with and including S: or C:) to stdin on the client and vice versa,
> until you either get success or failure.

That's what I did, and included in the original report, except that I
specified the service name ("host").  The results are the same if I
leave out the "-s host":

merlin at geomancer:~$ kinit
Password for merlin at NUTWERK.ORG: 
merlin at geomancer:~$ /usr/sbin/sasl-sample-server
Generating client mechanism list...
Sending list of 7 mechanism(s)
S: TE9HSU4gQ1JBTS1NRDUgR1NTQVBJIFBMQUlOIEFOT05ZTU9VUyBOVExNIERJR0VTVC1NRDU=
Waiting for client mechanism...

merlin at geomancer:~$ sasl-sample-client -m gssapi -n geomancer.nutwerk.org
Waiting for mechanism list from server...
S: TE9HSU4gQ1JBTS1NRDUgR1NTQVBJIFBMQUlOIEFOT05ZTU9VUyBOVExNIERJR0VTVC1NRDU=
recieved 53 byte message
Forcing use of mechanism gssapi
Choosing best mechanism from: gssapi
sasl-sample-client: SASL Other: GSSAPI Error: Miscellaneous failure (Generic error (see e-text))
error was SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (Generic error (see e-text))
sasl-sample-client: Starting SASL negotiation: generic failure
merlin at geomancer:~$  echo $?
1
merlin at geomancer:~$ 


Any idea what I might be doing wrong?

  --Mike