macOS Add Serial Numbers

[varsis]

Hi,

Well As I am fairly new I would like to know how I would add a serial number box to my program. How to set up and everything Im a complete newb lol.

Any help is appreciated!

Thanks
Chris

 

[mufflon]

it depends on what you code in - is it C, java, basic or some of the other thousand or so languages?

basicly it's just another GUI element - whatever is written there needs to be validated, if it is a genuine key you will need to save this somewhere on the host computer.

A general question can only get a general response, no?

 

[varsis]

Well, Right now I am programming in Obj-c. I don't even have a clue were to start. Any thing you could send at me, show me in the right direction would be great.

Chris

 

[sord]

I'm sure you don't want to think about this at this point in time, however you want to also look into how to make it more secure. If its Obj-C, it can still be disassembled (machonist), decompiled (code-dump), etc, and where/how you store that the user is registered is important too.

I would suggest using the serial/machine number/activation number scheme. Throw in any little programming trick you can, such as writing your registration validation and storing in C, and call it using function pointers instead of just calling it. Also, obfuscate your method names.

Or you could go the framework route, and use or purchase someone's framework whose already thought of and handled these issues. I can't think of the names, but there are some good free and commercial ones out there.

 

[kainjow]

Well, Right now I am programming in Obj-c. I don't even have a clue were to start. Any thing you could send at me, show me in the right direction would be great.

Check out AquaticPrime.

 

[SC68Cal]

Also, obfuscate your method names.

I'm sorry, but you're an idiot. The time wasted trying to obfuscate your code is completely worthless. Not to mention, this is going to make things more difficult for you because when you go back to update the code you're going to be completely lost.

where/how you store that the user is registered is important too.

If you store that information in the code, people are going to find it. End of story. Don't do it.

Just focus on making something that someone will want to buy.

 

[sord]

I'm sorry, but you're an idiot. The time wasted trying to obfuscate your code is completely worthless. Not to mention, this is going to make things more difficult for you because when you go back to update the code you're going to be completely lost.

And you're ignorant - there are tools to do it for you on your release build so your code stays nice and maintainable. The more understandable your method names are, the easier it is for a "cracker" to come along and make sure everyone gets to use your software for free. The Objective-C compiler keeps method names in tact. Don't call someone an idiot just because you don't know what you're talking about.

If you store that information in the code, people are going to find it. End of story. Don't do it.

You clearly misunderstood what I was saying...