A server could list as a rule that you use their binaries. The player downloads a fresh copy and starts it. The program checksums itself and the data files the player already has and sends the results back. If everything is OK the user can start playing.
Every few days (more or less) the server would patch or recompile the program, if only to give it a different checksum.
This is probably a lot more complicated than I think but it might stop some cheaters.
First question: They will have to release it in.rpm,.deb,.tgz and any other package formats available. Second Question: Even if it works on Redhat, a related distro may use an older version of a package, ie libjpeg. Another example would be Corel compacting a 4 CD Debian distro into 1 CD. They may have tossed something important that SAS needs.
Slashdot Mirror
I have been thinking about this.
A server could list as a rule that you use their binaries. The player downloads a fresh copy and starts it. The program checksums itself and the data files the player already has and sends the results back. If everything is OK the user can start playing.
Every few days (more or less) the server would patch or recompile the program, if only to give it a different checksum.
This is probably a lot more complicated than I think but it might stop some cheaters.
First question: They will have to release it in .rpm, .deb, .tgz and any other package formats available. Second Question: Even if it works on Redhat, a related distro may use an older version of a package, ie libjpeg. Another example would be Corel compacting a 4 CD Debian distro into 1 CD. They may have tossed something important that SAS needs.
He is probably talking about replacing Exchange with something like Sendmail(depending on what He meant by shareware).