Cyrus SASL sample apps broken

Asked by Paul Lockyer

Hi,

I'm relatively new to Ubuntu so apologies if I've missed something obvious here. I have setup a clean install of Ubuntu 8.10 server on a VMware ESX host using the Ubuntu Server Edition installation CD by pressing F4 and choosing "Install a minimal virtual machine". I've tried a couple of times, once with none of the package groups selected, and once with the 'Basic Ubuntu server' set. Post installation I used apt to add the libsasl2-2 and sasl2-bin packages. Attempting to use the sasl-sample-server and sasl-sample-client applications results in the following exchange:

plockyer@ukknuld-svndev:~/tmp/cyrus-sasl-2.1.22/sample$ sasl-sample-server -s host
Generating client mechanism list...
Sending list of 7 mechanism(s)
S: Q1JBTS1NRDUgTE9HSU4gQU5PTllNT1VTIFBMQUlOIEdTU0FQSSBOVExNIERJR0VTVC1NRDU=
Waiting for client mechanism...

plockyer@ukknuld-svndev:/$ sasl-sample-client -s host -n ukknuld-svndev.tt.local -u ukplockyer
service=host
Waiting for mechanism list from server...
S: Q1JBTS1NRDUgTE9HSU4gQU5PTllNT1VTIFBMQUlOIEdTU0FQSSBOVExNIERJR0VTVC1NRDU=
sasl-sample-client: Decoding data from base64: bad protocol / cancel

Running the applications as root (via sudo) makes no difference to the result. I believe that the Kerberos side of things is OK as I can run kinit and get a ticket granting ticket OK (plus from where the sample apps fail I suspect that no attempt has been made to contact the KDC). If I download the source for Cyrus SASL and compile it the sample apps run correctly without the error above, so I suspect that this may be a bug in the packaged version (but then I could just be doing something wrong).

Any suggestions as to how to resolve this issue would be welcome.

Thanks..

Paul.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu cyrus-sasl2 Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
donapieppo (donapieppo) said :
#1

Try to paste S: Q1JBTS1NRDUgTE9HSU4gQU5PTllNT1VTIFBMQUlOIEdTU0FQSSBOVExNIERJR0VTVC1NRDU= and then
ctrl+D insted of the enter key.
The problem seems related to line terminators in base 64 decoding.

Ciao
Pietro

Can you help with this problem?

Provide an answer of your own, or ask Paul Lockyer for more information if necessary.

To post a message you must log in.