Cheat Engine

[The0neThe0nly]

Hey I made a program recently and I want to make it require you to log in to access the program.

I need to be able to create the "accounts" too.

Is there an easy way I can protect my program with this kind of system?

It would be helpful if I could possibly "shut down" accounts too.

[NotReallySureWhatGoesHere]

Using authentication is the way to go, or at least it always helps!

http://oauth.net/code/

Then on your server side, have some type of database MySQL, PostgreSQL, etc. and have it check for the username/password/id/etc. That's how I'd do it.

EDIT: If you want to lock an account I'd make a field in the database called "enabled" and set that to 0 or 1, also have your application check it.

[Innovation]

There's no indefinite way to prevent people from cracking your program, but DRM might help fend them off for a while.

[Slugsnack]

[atom0s]

If you plan on using some sort of login system, you will need to be doing more to prevent people from using your application than just a simple 'Failed to login!' screen. Like Slug said, you'd be better off just not having any security then. You will need to extend your protection(s) to prevent the client from working. Such as:

- Crc32 checks (Prevent modifications to your binary.)
- Md5 checks (Prevent modifications to your binary.)
- Streamed data chunks
- Streamed required data (offsets, pointers, etc.)

Your best options are going to be streaming portions of your code to require the application to have a valid connection to your server. Which you can bind sessions to levels of access, as well as banning them from your application.

If you stream portions of the code that are the main body of your application it will prevent cracking from happening easily without a valid account. Not to say it wont happen ever, it will just be harder then.

Either way, there is no good answer for this. Any type of protection you come up with will have its own flaws.

[NotReallySureWhatGoesHere]