I have found some similar code in function TCustomLineWSocket.DoRecv() from
ICS-V5:
===
--- D:/DelphiComponents/Ics/Delphi/Vc32/WSocket.pas (revision 279)
+++ D:/DelphiComponents/Ics/Delphi/Vc32/WSocket.pas (working copy)
@@
Tobias Rapp wrote:
I have found some similar code in function
TCustomLineWSocket.DoRecv() from ICS-V5:
I don't think it is a bug in ICS-V5, since Buffer mostly was of
no type (if memory serves well). This changed in ICS V6 where
Buffer is of type TWSocketData which maps to Pointer in Win32.
Arno Garrels wrote:
I don't think it is a bug in ICS-V5, since Buffer mostly was of
no type (if memory serves well). This changed in ICS V6 where
Buffer is of type TWSocketData which maps to Pointer in Win32.
That's true. As a programmer coming from C language the typeless var Buffer
thing
Fastream Technologies wrote:
I think a C compiler would complain if you pass a char instead of
char* in compile time. That's what I meant.
Look at the declaration of Move() that makes it clear.
--
Arno Garrels
On Sun, Nov 1, 2009 at 8:07 PM, Arno Garrels arno.garr...@gmx.de
wrote:
support mailing twsocket@elists.org
Sent: Sunday, November 01, 2009 9:35 PM
Subject: Re: [twsocket] Serious bug in
TWSocket(AVorbufferoverflow)Pleasehelp !
Fastream Technologies wrote:
I think a C compiler would complain if you pass a char instead of
char* in compile time. That's what I meant
