Compiler dead space is it all the same ?
#3
(08-20-2023, 11:08 AM)bplus Wrote: I know you can spot a QB64 exe from another exe but not sure you can get the version also?

Version is not really the problem.
The following is not a thing anymore.  Long ago to infect an exe the virus code was tacked on the end and redirect the start point.  Antivirus could detect larger file than normal.  Next infect point was to use the compiler's dead space in the EXE and jump in there.  To kill that one, PXE packing was added to EXE files.  My problem still exists, the dead space after unpacking the PXE still holds the random data.  Which would change the SHA hash every time.

Unless you are really into open source fully.  Being sure the open code compiles like the original writer's code is hard.  That's one of the reasons original coders will only publish the exe and hash today.  A prefect problem with that is glaringly evident in the "BEST" sorter program out there.  QSORT!  Nobody has the original code at all.  The author took it to the grave.

IMHO, qsort will see no more improvements, even running in windows is a DOS emulation requirement.  QB64pe will not suffer the death like qsort did.  Because wise men chose open source.
Reply


Messages In This Thread
RE: Compiler dead space is it all the same ? - by doppler - 08-20-2023, 12:02 PM



Users browsing this thread: 6 Guest(s)