Is it a real buffer overflow, the kind that Microsoft is infamous for and that makes Microsoft software Swiss cheese software? Or is it a potential buffer overflow that is being trapped? Since it generates an error message, I suspect that it's a trapped buffer overflow, IOW the overflow doesn't actually happened but is caught before it happens. Ideally, they would have designed the system to handle anything that we are likely to throw at it, but at least they put in some hooks to trap for it.
There - I've actually said something somewhat positive about Valve instead of my usual criticism :-P
----- Original Message ----- From: "Whisper" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 30, 2004 5:25 PM Subject: Re: [hlds] Console buffer overflow - Preventing large file execution
How about the crazy idea of not programming in a way that allow buffer overflows to occur in the first place?
This is not the only one, and won't be the last and its always a case of sticking fingers in dykes until the job is done correctly.
Whats the odds the next HLDS or STEAM exploit won't be manifest itself in a buffer overflow?
Or are the odds that short nobody would take the bet?
On Wed, 1 Dec 2004 11:15:20 +1100, Andrew Armstrong <[EMAIL PROTECTED]> wrote:
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hey,
Due to there being a restriction on the amount of text the console buffer will show when executing a file, large files (such as a server banlist file) are not even being attempted to be executed because the console returns an error, 'CBuf_AddText: buffer overflow' (Console buffer, addtext procedure - buffer overflow).
Ive been trying to find a workaround for this limitation, but have had no luck. There does not seem to be any way to disable the console, suppress console feedback (even temporarily), or any way to silently execute files.
Executing the file via the commandline, console, having the file inside another file and executing that parent file etc all return the same buffer overflow problem.
Apparently this is a known issue by Valve, and a fix would be good, because besides rendering a decent banlist useless (since you cant execute it - and no, splitting the banlist into several files is not an acceptable fix), even some user created scripts/config files are too large to be executed.
Valve, if there is a way we can suppress console feedback, or adjust the amount of permitted buffer space in the console just so the file can be run, please let us know.
Cheers, Plasma --
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
