beepcore-java-users

[Beepcore-java-users] Possible bug in SASL profile listener code

[Paul A. <paa...@ci...>]

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.

Re: [Beepcore-java-users] Possible bug in SASL profile listener code

[Huston <hu...@us...>]

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

RE: [Beepcore-java-users] Possible bug in SASL profile listenercode

[Paul A. <paa...@ci...>]

No problem.

> -----Original Message-----
> From: Huston [mailto:hu...@us...] 
> Sent: Thursday, May 29, 2003 11:59 AM
> To: Paul Andrews
> Cc: Bee...@li...
> 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
>