I've started to work on semi work-related projects - i.e. it uses Six Apart technology stack, and I code mostly during the night but also I use my hackathon time to do stuff.
I thought I'd document all the quircks I've found in my way. First it will allow me to remember all this stuff, and second I think it's me being a good internet citizen (someone will find this page someday using google, and might get helped this way).
It might not be that interesting other than for this documentation purpose though.
I intstalled virtual box and ubuntu on my mac, and found two issues with vboxsf (shared folders for ubuntu):
the first one is a problem with linux's sendfile and the second is auto-completion (probably related to vboxsf)
I'm adding pure Perl support for servers in Authen::SASL module, and then hooking that into DJabberd. Doing so, I noticed (thanks hachi for the long debugging session, not related to Danga::Socket/DJabberd at all!), than Psi is not sending the xml (stream start after a successful SASL negotiation) that is shown in its own xml-console!
That last thing made me switched to Adium. And there I noticed a weird issue in the challenge parsing of DIGEST_MD5. I noticed extra quote (") in the realm and digest_uri. I temporarily fixed by changing the order of my tokens inside of the challenge and it fixed the issue... but I have to investigate more, it looks like a libpurple bug.
Lots of TODO and TOFIX!
I've tried with iChat, and it comes with its own set of issues:
Jan 7 17:27:54 yann iChatAgent: [SASL] Level 5: DIGEST-MD5 unrecognized pair cipher-opts/rc4, 3des, des, rc4-56, rc4-40: ignoring
Jan 7 17:27:54 yann iChatAgent: [SASL] Level 5: DIGEST-MD5 unrecognized pair qop-options/auth, auth-inf, auth-conf: ignoring
multiple pair doesn't work either:
Jan 7 21:09:56 yann iChatAgent: [SASL] Level 5: DIGEST-MD5 unrecognized pair qop-options/auth-conf: ignoring
Jan 7 21:09:56 yann iChatAgent: [SASL] Level 5: DIGEST-MD5 unrecognized pair qop-options/auth-inf: ignoring
Jan 7 21:09:56 yann iChatAgent: [SASL] Level 5: DIGEST-MD5 unrecognized pair qop-options/auth: ignoring
damnit! I know that DIGEST-MD5 is not the most useful mechanism for me, but still...
I'm going to check if this is me that doesn't interpret the RFC 2831 correctly though.
Alright, rechecking the RFC/my code it looks like it's not "qop-options" but "qop" and "cipher" and not "cipher-opts". iChat is fine, psi for some reason is behaving weirdly (not sending data to the socket, this is mysterious), Adium has probably issues with challenge parsing (when the challenge includes unsupported token?)