Besides your own pitiful, whining imagination, what documentary evidence do you have that John Carmack is deliberately helping cheaters?
When the Cheaters first appeared, A COUPLE OF YEARS BEFORE the Quake Source release, what effective action did you take against them?
Did you organize any community effort to track the lamers down (using the net.gods amongst the Quake player *community*) and punish them so thoroughly that anyone even thinking about cheating after that would have nightmares?
If not, then you are way the hell out of line to be whining about them now!
> - thats his deal - and his right...but - >lets look of what he done, and its consequenses >instad of the very nice, but bottomline - >totally unintersting part about GPL me this and that.. >GPL doesnt help the cheater or anticheater - >it has no impact on the game..
The Cheaters had already cracked the weakly designed Quake network protocols and created the first radars and aimbots within a few short months after the initial Quake release. They obtained their OWN *assembler* source code by reverse engineering.
GPL helps the anti-cheater more than it does the cheater, despite how things may appear for the near term.
Opening the Quake source has made if possible for hundreds of very bright, creative and security-knowledgable Internet programmers to review the security model of the Quake Network protocols and come up with a strong long-term solution, if one exists.
What are you doing to help ensure that happens - besides whing about John Carmack?
[BR]Sneaky! AHL Clan Bloodrush long term Quake, TF and MegaTF player email: mhobson@pacbell.net
I have devised a method whereby a fully open-sourced network client might be reliably verified as a 'blessed binary' by the server:
(1)which cannot be spoofed by simply scanning a file copy of the valid binary and generating the appropriate checksum/hash/etc. - it requires the *exact unmodified* binary to be in memory and actually executing.
and
(2)and which would simultaneously provide cryptographic signatures for each client information pack that could not be correctly generated by any sort of proxy (aimbots are proxies).
This proposal is highly theoretical and has not yet been implemented. I would like to discuss it with any technically competent programmers.
Slashdot Mirror
>That Its very nice John want to support cheaters
Besides your own pitiful, whining imagination, what documentary evidence do you have that John Carmack is deliberately helping cheaters?
When the Cheaters first appeared, A COUPLE OF YEARS BEFORE the Quake Source release, what effective action did you take against them?
Did you organize any community effort to track the lamers down (using the net.gods amongst the Quake player *community*) and punish them so thoroughly that anyone even thinking about cheating after that would have nightmares?
If not, then you are way the hell out of line to be whining about them now!
> - thats his deal - and his right...but -
>lets look of what he done, and its consequenses
>instad of the very nice, but bottomline -
>totally unintersting part about GPL me this and that..
>GPL doesnt help the cheater or anticheater -
>it has no impact on the game..
The Cheaters had already cracked the weakly designed Quake network protocols and created the first radars and aimbots within a few short months after the initial Quake release. They obtained their OWN *assembler* source code by reverse engineering.
GPL helps the anti-cheater more than it does the cheater, despite how things may appear for the near term.
Opening the Quake source has made if possible for hundreds of very bright, creative and security-knowledgable Internet programmers to review the security model of the Quake Network protocols and come up with a strong long-term solution, if one exists.
What are you doing to help ensure that happens - besides whing about John Carmack?
[BR]Sneaky!
AHL Clan Bloodrush
long term Quake, TF and MegaTF player
email: mhobson@pacbell.net
I have devised a method whereby a fully open-sourced network client might be reliably verified as a 'blessed binary' by the server:
(1)which cannot be spoofed by simply scanning a file copy of the valid binary and generating the appropriate checksum/hash/etc. - it requires the *exact unmodified* binary to be in memory and actually executing.
and
(2)and which would simultaneously provide cryptographic signatures for each client information pack that could not be correctly generated by any sort of proxy (aimbots are proxies).
This proposal is highly theoretical and has not yet been implemented. I would like to discuss it with any technically competent programmers.
[BR]Sneaky! (AHL Clan BloodRush)
email: mhobson@pacbellnet
[BR