Hello again, you suxfoos.
Quote:
Originally Posted by Overlord
Here are some methods I had in mind:
- Size and MD5/CRC32 of the exe or some internal parts of it
- Window captions and class names
- Search for certain text strings within the process
- Spy the APIs to see if any program is using an API to memory edit Jazz 2
|
Yeah, but this also poses a security risk, people hosting servers could find people's credit card numbers and stuff.
Quote:
Originally Posted by Franken-Stijn
I've been thinking recently that something like an OpenJazz2 is perhaps our only solution to the mass-hacking that is taking place. Jazz2 is vulnerable to memory and packet editing, which allows for some pretty cool tweaks, but also to a lot of cheating. The problem is, ofcourse, that an OpenJazz2 would need a large amount of time and a few programmers who know what they're doing. And I doubt anyone would be willing to invest so much time in it.
|
You mean me? Well, I have some spare time that I could work on it. However, since the list servers are run by (-)s, then nah, forget it.
Now to answer more stuff before I go back to lurking.
__________________
UNKNOWNFILE's old account.
Blubberfish: Project abandoned
|