Programming Bits

Two Hundred Forty Third Post: Programming Bits

I’m still reading a little about C++. I mix it in with some other projects so it doesn’t get boring just studying the material. One thing that is learned about “classes” is that the variables could be “public” or “private.” This is to keep the variables to be written to unintentionally. Now the interesting part. If you did have access to these variables, you would basically be able to control how the program runs. I don’t know how you would go about it, but if the method was found, the program would be hacked.

Another way to hack (which I would like to know how) is to modify the DLL files. Since the program accesses these files, if the DLL is changed the program is hacked. That is why Quake 3 didn’t use DLL. If a mod was made the writer of the DLLs would have access to the users entire computer.

The book “Hacking Exposed” states that only a few percent of the computer user population has enough knowledge create or discover ways to defeat security. However, it goes on to say that once these vulnerabilities become known anyone can use them.

Just a little look at the hacking world. When you are first learning programming, you may wonder how anyone can hack something that is so complex. I guess it is just like any other project in that the user learns over time tinkering until hopefully a security flaw (or discovery) happens.

But until you find that security leak... May the Creative Force be with You

References:
Focus on Mod Programming in Quake III Arena, Shawn Holmes
Sams Teach Yourself C++ in 24 Hours, Jesse Liberty
Hacking Exposed Fourth Edition, Stuart McClure, Joel Scambray, George Kurtz