The real fix is to not depend on the contents of the file to determine the size of a static memory allocation; but there may be some security implications to be considered here before making that change.
I'd say the opposite is true. This sounds like a whopping big security hole as it is right now. Dear my... what if I had the file request 0x7654321, or 0xfee15bad ? (consider both signed and unsigned integer overflow) The quick hack is probably to multiply the allocations by 2. You could use sizeof(void*)/sizeof(int) if you like. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
