Re: [twsocket] SSL problem (server stops receiving data)

2016-02-02 Thread Merijn Bosma

Thanks for the update Angus!

Merijn

On 2/1/2016 20:42, Angus Robertson - Magenta Systems Ltd wrote:

We've hired someone to look into this issue, this resulted in
finding the probable cause of this issue, and a fix.
It would be great if someone could sort of validate the
conclusion and fix.
If all is OK, how to get these changes into the ICS codebase?

Your developer updated a six month old WSocket, so I added your changes
to the latest version.

Building your test application with the old v8.21 causes SSL to die
within a second, with the new V8.22 it works OK creating a gigabyte SSL
log file with lots of successful requests.

I don't understand why your fix works, it seems to execute the same
code as before, just in a different place, but clearly there was an SSL
problem before in your particular circumstance with overlapping
requests which is now fixed.

I've rebuilt my web application server and put it on my public web site,
where it will get a few hundred thousand requests quickly, although
I've not knowingly had any problems before.  If there are no new
problems, I'll updated SVN in a few days. My test page showing ICS
versions is at:

https://www.telecom-tariffs.co.uk/serverinfo.htm

Angus



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SSL problem (server stops receiving data)

2016-01-29 Thread Merijn Bosma

Hi All,

We've hired someone to look into this issue, this resulted in finding 
the probable cause of this issue, and a fix.

It would be great if someone could sort of validate the conclusion and fix.
If all is OK, how to get these changes into the ICS codebase?

Thanks,

Merijn


On 12/8/2015 17:42, Angus Robertson - Magenta Systems Ltd wrote:

I really hope someone can take a look at this, maybe confirm if the
problem is reproducible and see if I'm doing something wrong or this is
indeed a problem inside ICS / OpenSSL.

Sorry, I will not have any time to investigate for several weeks, or longer.
Maybe another volunteer here has more free time than I can spare.

Angus



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SSL problem (server stops receiving data)

2016-01-29 Thread Angus Robertson - Magenta Systems Ltd
> We've hired someone to look into this issue, this resulted in 
> finding the probable cause of this issue, and a fix.
> It would be great if someone could sort of validate the 
> conclusion and fix.
> If all is OK, how to get these changes into the ICS codebase?

Zip any ICS units and test applications you created and email them to
my email address.  If the changes are 'safe', I'll update SVN.

Angus 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SSL problem (server stops receiving data)

2015-12-08 Thread Angus Robertson - Magenta Systems Ltd
> I really hope someone can take a look at this, maybe confirm if the 
> problem is reproducible and see if I'm doing something wrong or this is 
> indeed a problem inside ICS / OpenSSL.

Sorry, I will not have any time to investigate for several weeks, or longer. 
Maybe another volunteer here has more free time than I can spare. 

Angus

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SSL problem (server stops receiving data)

2015-11-24 Thread Merijn Bosma

Hi Angus,

I agree with what you are saying, but in this case this is not the problem.

The only reason this app works like this, is because this seems to be 
the easiest way to reproduce this same issue which happens in a larger 
app, which does use a FIFO etc.
Log clearly shows that the two random numbers are being received 
separately on the server side.


Merijn

On 24/11/2015 17:23, Angus Robertson - Magenta Systems Ltd wrote:

The problem is triggered, when we do two times PostMessage(WM_USER)
in the OnSslHandshakeDone event, expected behavior would be that
the client sends a random number twice, server receives the first,
sends x bytes and term char, client receives it, sends next random
number (3th), server might be handling the 2nd number, etc.

I'd expect the client to send a single TCP/IP packet with both random numbers 
in it,
and for the server to receive both together.

So does the server have a FIFO buffer to store the second number for processing
later, that take priority over anything received.  I had this problem a long 
time
ago with a simple packet protocol.

The difference between SSL and non-SSL might be packets being combined.

Try putting a delay in when sending, so there is always a two or longer second 
gap
and see if the problem goes away.  But the real solution is the FIFO buffer.

Angus




--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] SSL problem (server stops receiving data)

2015-11-24 Thread Angus Robertson - Magenta Systems Ltd
> The problem is triggered, when we do two times PostMessage(WM_USER) 
> in the OnSslHandshakeDone event, expected behavior would be that 
> the client sends a random number twice, server receives the first, 
> sends x bytes and term char, client receives it, sends next random 
> number (3th), server might be handling the 2nd number, etc.

I'd expect the client to send a single TCP/IP packet with both random numbers 
in it,
and for the server to receive both together.  

So does the server have a FIFO buffer to store the second number for processing
later, that take priority over anything received.  I had this problem a long 
time
ago with a simple packet protocol.  

The difference between SSL and non-SSL might be packets being combined. 

Try putting a delay in when sending, so there is always a two or longer second 
gap
and see if the problem goes away.  But the real solution is the FIFO buffer.  

Angus


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be