On Mon, 2004-02-09 at 18:36, Robert Norris wrote: > On Mon, Feb 09, 2004 at 01:57:31PM -0500, Bob Phan wrote: > > I'm using Authen::SASL 2.06 with perl to try to authenticate a component > > to j2. As far as I can tell, the response it is generating is accurate, > > however I'm still getting errors. If anyone has any idea as to why this > > isn't working, I'd appreciate any and all help. > > Debug logs from the server may help. However, I suspect this is the > "qop" bug that is present in s1. s2 will fix it; I hope to have it out > today (my time, ie some time in the next eight hours).
I installed s2 with the configure option to enable debug messages. It's still not working. Here's debug output from the server and my client. Server: ROUT: sx (sasl.c:230) sasl context initialised for 12 ROUT: Tue Feb 10 14:23:14 2004 scod.c:255 server start ROUT: Tue Feb 10 14:23:14 2004 scod.c:151 looking for mech 'DIGEST-MD5' ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:413 DIGEST-MD5 server start ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:63 escaped 'jabberd-router' into '"jabberd-router"' ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:246 generated nonce: b920deb17ce4afdd0bdb8374f90b4fe01c18d066 ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:63 escaped 'b920deb17ce4afdd0bdb8374f90b4fe01c18d066' into '"b920deb17ce4afdd0bdb8374f90b4fe01c18d066"' ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:442 generated initial challenge: realm="jabberd-router",nonce="b920deb17ce4afdd0bdb8374f90b4fe01c18d066",qop="auth",charset=utf-8,algorithm=md5-sess ROUT: Tue Feb 10 14:23:16 2004 [notice] [127.0.0.1, port=1155] disconnect ROUT: sx (sasl.c:274) sasl handshake in progress (challenge: realm="jabberd-router",nonce="b920deb17ce4afdd0bdb8374f90b4fe01c18d066",qop="auth",charset=utf-8,algorithm=md5-sess) ROUT: sx (chain.c:106) calling nad write chain ROUT: sx (io.c:353) queueing for write: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImphYmJlcmQtcm91dGVyIixub25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge> ROUT: sx (io.c:205) tag 12 event 1 data 0x0 ROUT: Tue Feb 10 14:23:14 2004 router.c:494 want write ROUT: Tue Feb 10 14:23:14 2004 router.c:842 write action on fd 12 ROUT: sx (io.c:277) 12 ready for writing ROUT: sx (io.c:235) encoding 220 bytes for writing: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImphYmJlcmQtcm91dGVyIixub25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge> ROUT: sx (chain.c:79) calling io write chain ROUT: sx (io.c:296) handing app 220 bytes to write ROUT: sx (io.c:297) tag 12 event 3 data 0x80c2b68 ROUT: Tue Feb 10 14:23:14 2004 router.c:564 writing to 12 ROUT: Tue Feb 10 14:23:14 2004 router.c:568 220 bytes written ROUT: sx (io.c:330) tag 12 event 0 data 0x0 ROUT: Tue Feb 10 14:23:14 2004 router.c:489 want read ROUT: Tue Feb 10 14:23:14 2004 router.c:831 read action on fd 12 ROUT: sx (io.c:143) 12 ready for reading ROUT: sx (io.c:149) tag 12 event 2 data 0x80c2b68 ROUT: Tue Feb 10 14:23:14 2004 router.c:499 reading from 12 ROUT: Tue Feb 10 14:23:14 2004 router.c:557 read 408 bytes ROUT: sx (io.c:165) passed 408 read bytes ROUT: sx (chain.c:93) calling io read chain ROUT: sx (io.c:189) decoded read data (408 bytes): <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> ROUT: Y2hhcnNldD11dGYtOCxjbm9uY2U9Ijg1MDlkOTAxNmY5NDkxMTA0MGZiNGVmMTRjODJiM2RmIixk ROUT: aWdlc3QtdXJpPSJ4bXBwL2oyLmRldmlhbnR0ZWNobm9sb2dpZXMuY29tIixuYz0wMDAwMDAwMixu ROUT: b25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRo ROUT: IixyZWFsbT0iamFiYmVyZC1yb3V0ZXIiLHJlc3BvbnNlPWIxMjRiYTQwNzA0MThhZjQ3MDkwNjNm ROUT: ZjM5ZmM5YzdkLHVzZXJuYW1lPSJsb2dnZXIi ROUT: </response> ROUT: sx (io.c:65) completed nad: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> ROUT: Y2hhcnNldD11dGYtOCxjbm9uY2U9Ijg1MDlkOTAxNmY5NDkxMTA0MGZiNGVmMTRjODJiM2RmIixk ROUT: aWdlc3QtdXJpPSJ4bXBwL2oyLmRldmlhbnR0ZWNobm9sb2dpZXMuY29tIixuYz0wMDAwMDAwMixu ROUT: b25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRo ROUT: IixyZWFsbT0iamFiYmVyZC1yb3V0ZXIiLHJlc3BvbnNlPWIxMjRiYTQwNzA0MThhZjQ3MDkwNjNm ROUT: ZjM5ZmM5YzdkLHVzZXJuYW1lPSJsb2dnZXIi ROUT: </response> ROUT: sx (chain.c:119) calling nad read chain ROUT: sx (sasl.c:247) response from client ROUT: Tue Feb 10 14:23:14 2004 scod.c:296 server step ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:457 DIGEST-MD5 server step; response: ROUT: Tue Feb 10 14:23:14 2004 mech_digest_md5.c:510 returning error 34 ROUT: sx (sasl.c:291) sasl handshake failed: (34) ROUT: sx (chain.c:106) calling nad write chain ROUT: sx (io.c:353) queueing for write: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><temporary-authentication-failure/></failure> ROUT: sx (io.c:205) tag 12 event 1 data 0x0 ROUT: Tue Feb 10 14:23:14 2004 router.c:494 want write ROUT: Tue Feb 10 14:23:14 2004 router.c:842 write action on fd 12 ROUT: sx (io.c:277) 12 ready for writing ROUT: sx (io.c:235) encoding 95 bytes for writing: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><temporary-authentication-failure/></failure> Client: Tue Feb 10 14:23:14 2004: Sent: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' > Tue Feb 10 14:23:14 2004: Recd: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' id='igpk13gsx78ebciounvxql9w670zdqav70g93w21'><stream:features xmlns:stream='http://etherx.jabber.org/streams'><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features> INIT FINISHED! Tue Feb 10 14:23:14 2004: Sent: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5' /> Tue Feb 10 14:23:14 2004: Recd: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImphYmJlcmQtcm91dGVyIixub25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge> Caught a challenge!!!! Server send us a challenge, we will now respond to it.Decoded from server: realm="jabberd-router",nonce="b920deb17ce4afdd0bdb8374f90b4fe01c18d066",qop="auth",charset=utf-8,algorithm=md5-sess Here's our decoded response: charset=utf-8,cnonce="dcd77f457d56df3fa8bb2436dbc6c208",digest-uri="xmpp/j2.devianttechnologies.com",nc=00000001,nonce="b920deb17ce4afdd0bdb8374f90b4fe01c18d066",qop="auth",realm="jabberd-router",response=6435053319f61e7339ce4d4b1ed82e9e,username="logger" Tue Feb 10 14:23:14 2004: Sent: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> Y2hhcnNldD11dGYtOCxjbm9uY2U9Ijg1MDlkOTAxNmY5NDkxMTA0MGZiNGVmMTRjODJiM2RmIixk aWdlc3QtdXJpPSJ4bXBwL2oyLmRldmlhbnR0ZWNobm9sb2dpZXMuY29tIixuYz0wMDAwMDAwMixu b25jZT0iYjkyMGRlYjE3Y2U0YWZkZDBiZGI4Mzc0ZjkwYjRmZTAxYzE4ZDA2NiIscW9wPSJhdXRo IixyZWFsbT0iamFiYmVyZC1yb3V0ZXIiLHJlc3BvbnNlPWIxMjRiYTQwNzA0MThhZjQ3MDkwNjNm ZjM5ZmM5YzdkLHVzZXJuYW1lPSJsb2dnZXIi </response> Tue Feb 10 14:23:14 2004: Recd: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><temporary-authentication-failure/></failure> I didn't see anything too helpful in the server output except the error number 34. Does that mean anything special? Also, I was curious if there exists any test application which uses the SASL DIGEST-MD5 mechanism for authentication that you know works. I would like to use this to test my server configuration to ensure that my problem is client-side. Thanks again for your help and patience. -- /* * Bob Phan <[EMAIL PROTECTED]> * Code Master General * Deviant Technologies Incorporated * (203)458-2312 * * http://www.devianttechnologies.com/ */ _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
