RE: Possible bug in SASL profile listenercode

"Paul Andrews" <[email protected]> Thu, 29 May 2003 12:20:34 -0400
Newsgroups gmane.network.beep.beepcore.java.general
Message-ID <[email protected]>
No problem.

> -----Original Message-----
> From: Huston [mailto:[email protected]] 
> Sent: Thursday, May 29, 2003 11:59 AM
> To: Paul Andrews
> Cc: [email protected]
> Subject: Re: [Beepcore-java-users] Possible bug in SASL 
> profile listenercode
> 
> 
> On Thu, 2003-05-29 at 09:01, Paul Andrews wrote:
> > At various places, the SASL tuning profile listener code 
> sends a blob
> > containing <abort>s to the initiator if anything goes wrong. I don't
> > think this is correct. RFC 3080 says:
> >  
> > exchange sequence: 
> >         "Challenges" and "responses" are carried in exchanges of the
> >         "blob" element. The "status" attribute of the "blob" element
> >         is used both by a server indicating a successful 
> completion of
> >         the exchange, and a client aborting the exchange, The server
> >         indicates failure of the exchange by sending an "error"
> >         element.
> 
> I agree with your assesment, this needs to be fixed in beepcore-j.
> 
> Would you mind entering this as a bug on SF so that is doesn't get
> forgotten about?
> 
> --Huston
> 



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5