Trustin,

Thanks for incorporating a fix.  I was able to reproduce the problem at will
by invoking SSLSocket.startHandshake() in the client.  The fix that I wrote
resolved the infinite loop in the SSLHandler.unwrap, but now the handshake
status is NEED_WRAP and when I attempt to encrypt the next response I
receive a BUFFER_OVERFLOW error from the SSLEngine.  I'll give your fix a
try and let you know how it goes.  

Thanks,

JG


Trustin Lee wrote:
> 
> I've just checked in the fix for the infinite loop bug you found.
> 
> I didn't deploy the snapshot JAR yet, so you will have to build MINA
> by yourself.  Please refer to our developer guide on how to build the
> latest source code:
> 
> http://mina.apache.org/developer-guide.html
> 
> Please let me know if it fixes the problem.  If it doesn't, please
> provide DEBUG log.
> 
> Thanks,
> Trustin
> 
> On 7/30/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
>> Hi James,
>>
>> On 7/30/07, James Gould <[EMAIL PROTECTED]> wrote:
>> >
>> > The following is the code snippet within SSLHandler.unwrap() to ensure
>> that
>> > handshake tasks are taken care of instead of causing an infinite loop. 
>> Any
>> > thoughts or comments?
>>
>> The handshake status during unwrap() must be NOT_HANDSHAKING.
>> Otherwise, it means the connection entered renegotiation.  Did you
>> change cipher set or something else after handshake is finished?
>>
>> Anyway, unwrap doesn't properly handle renegotiation.  Thanks for
>> reporting a critical bug!  Let me try to fix the buf and reply to this
>> thread again.
>>
>> Thanks,
>> Trustin
>> --
>> what we call human nature is actually human habit
>> --
>> http://gleamynode.net/
>> --
>> PGP Key ID: 0x0255ECA6
>>
> 
> 
> -- 
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Endless-Loop-in-SSLHandler.unwrap-causing-Mina-Gateway-to-Hang-tf4166136s16868.html#a11857309
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.

Reply via email to