Re: [twsocket] FTPCli problem.
Hello Francois, FP> That remind me a site where a bluecoat system was installed. Bluecoat was FP> configured to scan for virus any file passing thru, even zipped files which FP> where unzipped. unfortunately Bluecoat failed with a certain size of file FP> and as seen from the user, the transfer failed. Once that Bluecoat feature FP> was turned off, everything went OK. The first thing that I asked the user to do is to disable all firewalls and antiviruses, it didn't help. Anyway, we still don't understand why only ICS 7 affected by this issue. Is it possible that there was a change between V5 and V7 in other dependant files (not FTPCli) that could lead to this problem? FP> You have to click on the TypeSet button which send the command to the FTP FP> server with the checkbox value as parameter. FP> Same as you have to do by code ! Really cool stuff, if you know how to use it, but give it to somebody else and his brain will boil from confusion! The absence of any manual for it makes a kind of guarantee that the user will be satisfied with this puzzle ;-) -- Best regards, Antolmailto:spama...@mail.ru -- 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] Send and Shutdown oddity
Arno Garrels wrote: > Markus Humm wrote: > > I mean if a message loop of 3 sec. doesn't give him enough time >>> Possibly the message loop isn't implemented properly? >>> Please show us some code. >> >> Ok, my message loop was constructed like this: >> >> var msg:TMessage; >>t:Dword; >> >> begin >> t:=GetTickCount; >> while (abs(GetTickCount-t) < 3000) do >> begin >>PeekMessage(msg, 0, 0, 0, pm_remove); >>TranslateMessage(msg); >>DispatchMessage(msg); >>sleep(20); >> end; >> end; > > That's most likely the cause, looks like an attempt to > workaround the async nature of ICS. A message loop should > use GetMessage and no Sleep(). And the loop should be terminated dynamically when it is no longer needed by posting a message i.e. the WM_QUIT message. If something blocks while in that loop 3 seconds might not be enough. It's also burning CPU cycles for nothingh since with every sleep a thread-switch is enforced. -- Arno Garrels -- 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] OT: 3Proxy malware?
Francois PIETTE wrote: >> Testing ICS against multiple proxy servers became more difficult. >> A check of 3Proxy.exe (http://www.3proxy.ru) at www.virustotal.com >> returned plenty of positives. Are they actually positives? >> Rather unlikely since it's open source IMO. > > Microsoft Security Essential also reports as "moderate risk" and > potentially dangerous. > See: > http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?name=Program%3aWin32%2fTinyProxy&threatid=138819 > > I understand this document only warn user that the program has a proxy > feature which is not by itself a real risk. That's my guess as well so I gave it a trial. It seems to support HTTP v1.0 only, so probably HTTP v1.0 is still in use by proxies and I have to add that to TWSocket as well. -- Arno Garrels -- 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] OT: 3Proxy malware?
Fastream Technologies wrote: > Dear Arno, > > Why don't you add our ICS-based IQ Proxy Server 5.0.0C1 to your test > againsts: > http://www.iqproxyserver.com Thanks for the hint, but as I understand it is a reverse proxy, I currently want to test the other direction with CONNECT requests (tunnel) including NTLM and Basic authentication. -- Arno Garrels -- 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] OT: 3Proxy malware?
Dear Arno, Why don't you add our ICS-based IQ Proxy Server 5.0.0C1 to your test againsts: http://www.iqproxyserver.com Regards, SZ On Sun, Feb 13, 2011 at 4:57 PM, Arno Garrels wrote: > Hi, > > Testing ICS against multiple proxy servers became more difficult. > A check of 3Proxy.exe (http://www.3proxy.ru) at www.virustotal.com > returned plenty of positives. Are they actually positives? > Rather unlikely since it's open source IMO. > > -- > Arno Garrels > -- > 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 > -- *Fastream Technologies* *Software IQ: Innovation & Quality* http://www.fastream.com | http://twitter.com/fastream | http://www.iqproxyserver.com | http://www.iqproxyserver.com/forum *Sales & Support: Email:* sa...@fastream.com, supp...@fastream.com | *Intl. Hotline:* +90-312-223-2830 (weekdays, 9am-6pm *GMT+200*) Join *IQ Proxy Server Yahoo group* at http://groups.yahoo.com/group/IQProxyServer Join *IQWF Server Yahoo group* at http://groups.yahoo.com/group/IQWFServer This is a *no-nonsense* signature! Please do *join our yahoo groups for announcements of future versions* of IQ Proxy Server and IQ Web/FTP Server (traffic level is *very low*). -- 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] OT: 3Proxy malware?
Testing ICS against multiple proxy servers became more difficult. A check of 3Proxy.exe (http://www.3proxy.ru) at www.virustotal.com returned plenty of positives. Are they actually positives? Rather unlikely since it's open source IMO. Microsoft Security Essential also reports as "moderate risk" and potentially dangerous. See: http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?name=Program%3aWin32%2fTinyProxy&threatid=138819 I understand this document only warn user that the program has a proxy feature which is not by itself a real risk. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- 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] Send and Shutdown oddity
Markus Humm wrote: I mean if a message loop of 3 sec. doesn't give him enough time >> Possibly the message loop isn't implemented properly? >> Please show us some code. > > Ok, my message loop was constructed like this: > > var msg:TMessage; >t:Dword; > > begin > t:=GetTickCount; > while (abs(GetTickCount-t) < 3000) do > begin >PeekMessage(msg, 0, 0, 0, pm_remove); >TranslateMessage(msg); >DispatchMessage(msg); >sleep(20); > end; > end; That's most likely the cause, looks like an attempt to workaround the async nature of ICS. A message loop should use GetMessage and no Sleep(). -- Arno Garrels -- 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
[twsocket] OT: 3Proxy malware?
Hi, Testing ICS against multiple proxy servers became more difficult. A check of 3Proxy.exe (http://www.3proxy.ru) at www.virustotal.com returned plenty of positives. Are they actually positives? Rather unlikely since it's open source IMO. -- Arno Garrels -- 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] Send and Shutdown oddity
> Markus Humm wrote: >> > Markus Humm wrote: >>> My application now has to tell the communication part (means the >>> server side of the TWSocket connection) to shut down. it sends him a >>> binary shutdown command and after a short time the client does a >>> shutdown(1) on the socket. >>> >> >>> >> There's most likely something wrong in your application logic. >>> >> When the server receives your custom shutdown command it should stop >>> >> listening first, send an OK-response back to the requesting client >>> >> and disconnect all client connections. >>> >> >>> >> On the client-side after sending your custom shutdown command, >>> >> receive the OK response and subsequently either Close the connection >>> >> actively or wait for the server to close the connection. However with >>> >> "wait" I do of course _not_ mean "wait in some loop", OnSessionClosed >>> >> fire on connection close. >>> >> >> > >> > That might be a option, but I'm not yet fully convinced. How long may >> > it take to send a short message to localhost and receive it on the >> > other side? > It depends. If blocking tasks are executed at that moment no window > messages can be processed and no data can be received. If server and > client are running in the same thread context one blocking task is > enough to block both client and server I/O. > >> > >> > I mean if a message loop of 3 sec. doesn't give him enough time > Possibly the message loop isn't implemented properly? > Please show us some code. Ok, my message loop was constructed like this: var msg:TMessage; t:Dword; begin t:=GetTickCount; while (abs(GetTickCount-t) < 3000) do begin PeekMessage(msg, 0, 0, 0, pm_remove); TranslateMessage(msg); DispatchMessage(msg); sleep(20); end; end; One thing I'm currently not sure of (will check tomorrow) whether the sending application also had its own thread for the TWSocket. If yes, then the waiting was in the main thread instead of the secondary thread. The message processing of the secondary thread would have been implemented with GetMessage then (at least out of my head). I'll check tomorrow. Greetings Markus -- 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] FTPCli problem.
> > zipped > > files which where unzipped. unfortunately Bluecoat failed with a > > certain size of file and as seen from the user, the transfer > > failed. > > Once that Bluecoat feature was turned off, everything went OK. > > That does not explain why it works with ICSv5. The firewall may have been set-up to ignore file transfers with specific named application or IP address. I reported an identical issue in this mailing list a few weeks ago where an FTP download kept failing at about 2 gigs, when a suspicious file was detected in a zipped virtual machine image by my Sonicwall firewall. I then added the IP address of the server to the whitelist to prevent checking again. 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] FTPCli problem.
Francois PIETTE wrote: >> OK, after another series of tests it turned out that I have no >> idea what the problem is. The user could find out that: >> >> - using a passive connection to transfer any file of a certain >> size (maybe larger than 38Mb but maybe 37.Mb) causes a >> failure under unknown conditions (the ftp client hangs). > > That remind me a site where a bluecoat system was installed. Bluecoat > was configured to scan for virus any file passing thru, even zipped > files which where unzipped. unfortunately Bluecoat failed with a > certain size of file and as seen from the user, the transfer failed. > Once that Bluecoat feature was turned off, everything went OK. That does not explain why it works with ICSv5. -- Arno Garrels -- 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] Send and Shutdown oddity
Markus Humm wrote: > Markus Humm wrote: >>> My application now has to tell the communication part (means the >>> server side of the TWSocket connection) to shut down. it sends him a >>> binary shutdown command and after a short time the client does a >>> shutdown(1) on the socket. >> >> There's most likely something wrong in your application logic. >> When the server receives your custom shutdown command it should stop >> listening first, send an OK-response back to the requesting client >> and disconnect all client connections. >> >> On the client-side after sending your custom shutdown command, >> receive the OK response and subsequently either Close the connection >> actively or wait for the server to close the connection. However with >> "wait" I do of course _not_ mean "wait in some loop", OnSessionClosed >> fire on connection close. >> > > That might be a option, but I'm not yet fully convinced. How long may > it take to send a short message to localhost and receive it on the > other side? It depends. If blocking tasks are executed at that moment no window messages can be processed and no data can be received. If server and client are running in the same thread context one blocking task is enough to block both client and server I/O. > > I mean if a message loop of 3 sec. doesn't give him enough time Possibly the message loop isn't implemented properly? Please show us some code. > why should the change of logic be better? Dunno, it's just how I would do it, following a simple request/response pattern. -- Arno Garrels -- 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] Send and Shutdown oddity
Another related question: are there two logical channels in the background of TCP, one for sending the actual data and one for signalling the close? Otherwise I cannot explain myself why the data doesn't arrive but the close does. There is only one channel. Actual data and signalling are using the same physical medium and are using the same packets. There are a number of headers in the packets which makes the distinction. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- 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] Send and Shutdown oddity
Markus Humm wrote: > > My application now has to tell the communication part (means the > > server side of the TWSocket connection) to shut down. it sends him a > > binary shutdown command and after a short time the client does a > > shutdown(1) on the socket. > > There's most likely something wrong in your application logic. > When the server receives your custom shutdown command it should stop > listening first, send an OK-response back to the requesting client and > disconnect all client connections. > > On the client-side after sending your custom shutdown command, > receive the OK response and subsequently either Close the connection > actively or wait for the server to close the connection. However with > "wait" I do of course _not_ mean "wait in some loop", OnSessionClosed > fire on connection close. > That might be a option, but I'm not yet fully convinced. How long may it take to send a short message to localhost and receive it on the other side? I mean if a message loop of 3 sec. doesn't give him enough time why should the change of logic be better? Another related question: are there two logical channels in the background of TCP, one for sending the actual data and one for signalling the close? Otherwise I cannot explain myself why the data doesn't arrive but the close does. Greetings Markus -- 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
