[jdev] tls + plain sasl not working

[Matthew A. Miller]

Your server isn't seeing a NULL in the stream, it's seeing the 
base64-encoded version of NULL.  During SASL authentication, it should 
be decoding that string, and handling it fine.

Also, I'd like to point out that you should only send the authzid if you 
are acting on behalf of someone else (which, in XMPP-land, is pretty 
rare).  Without the authzid, it's:
<null>authcid<null>password

Properly base64-encoded, of course.

Adrian Adrian wrote:
> Thanks for the info, guys.
>
> Still I'm very puzzled by this :
> authzid<null>authcid<null>passwd
>
> I'm connecting to my server through an xml socket. Wen I put a null 
> character there, wouldn't the server think it is the end of  the xml 
> message ?
>
>
>
>
>
>
>
> */Norman Rasmussen <norman at rasmussen.co.za>/* wrote:
>
>     On 3/22/06, Adrian Adrian wrote:
>     > Good point.
>     > One more question: In which format should I send the base64
>     information ?
>
>     http://www.ietf.org/internet-drafts/draft-ietf-sasl-plain-08.txt
>
>     As Bilyk points out the format is : optional
>     authzid<null>authcid<null>passwd
>
>     --
>     - Norman Rasmussen
>     - Email: norman at rasmussen.co.za
>     - Home page: http://norman.rasmussen.co.za/
>
>
> ------------------------------------------------------------------------
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls 
> <http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com> 
> to the US (and 30+ countries) for 2¢/min or less. 

-- 
-  LW

"Got JABBER(R)?" <http://www.jabber.org/>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3543 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20060323/9bfedf36/attachment-0002.bin>