EZQUAKE "SECURITY" MODULE HACK: ------------------------------- This archive will allow you to run a modified Ezquake client which passes all "security" checks done by other clients. REQUIREMENTS: ------------- o The original Ezquake release 1517 binaries. o The original Ezquake release 1517 "security" module. o This archive. PREPARATION: ------------ It's assumed that you have already got Quake, Ezquake release 1517 and the corresponding "security" module installed. Go to the ezquake_source_1517 directory and type make release. Assuming that you've got all the odd and strange libraries that Ezquake requires, this should give you a set of binaries inside the release-x86 directory. Copy your desired binary to your quake directory, but do NOT overwrite the original binary. Next up compile ezsec1517patch.c: gcc ezsec1517patch.c -o ezsec1517patch Then run: ./ezsec1517patch.c /path/to/ezquake-security.so /tmp/ezsecur Next make a link in /tmp/ezsecur to point to the original binary of the same type as you want to use modified. For example: ln -s /path/to/quake/ezquake-gl.glx /tmp/ezsecur Next up run your newly built Ezquake. If everything went well, the "security" module should work with your binary. If not, chances are the version string supplied at Security_Init() is wrong somehow (check the string). The client comes premodded with a "/hacked" command, as requested by oldman and hetman. NOTES: ------ The whole idea of clientside authentication is flawed. See my notes on it on http://bigfoot.morphos-team.net/misc/ezquake-security.html AUTHOR: ------- Redirect comments, flames, suggestions (flames mostly, I guess :) to Mark Olsen