forum.vdsworld.com

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

well i got the run program so many times working great BUT i have thought of something that is a problem..How do i make it so YOU can run the same s/n twice? otherwise all the person has to do is write the s/n down on paper then re-enter it in Sad

please post any ideas for a fix like this

thanks

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

You just have to keep track of how many times the serial number has been
used and then verify if it's correct. If it is, just reset the value of how many
times the program has been run for the serial number to 0.

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

yea thati s one idea OR have it uses diff pass keys...then you can have it STILL run the number of times without having to go up meaning

if a user need 2 runs and you do it the way you talked it would blacklist the number 2 s/n....if i have it save the pass-key and s/n like you said then you can still give a user 2 runs...

i hope i make sense...

when i'am done i will post it in the "open soruce code" can i post it there or should i post it elsewhere?

thanks

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

Here's something that might give you an idea:

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

ok i will post it in the open forums also to i have the code for entering the s/n just have to figure out how to have it check it....OR have it write the pass key within the s/n and have the program read the ini file and have it read so many btyes over and that would be the passkey then have it store it so you can't uses the same pass key and s/n twice....something like that..... Smile

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

well i still can't get it to check the s/n that is in the ini then if diff ok to run...also to i notice that when using ini files how do you make it NOT over write a line ? mean how to have ini do this:

line 1
line 2
line 3

problem that i'am having it overwrites the s/n and it don't store it when a new one is entered Sad

thanks

Dr. Dread · Posted: Sun Mar 30, 2003 6:36 pm Post subject:

If you don't want to overwrite your INI file values, then don't write to the INI file Wink

Nah, if you want to keep values in your INI file, then assign each value to a different key, like this:

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

well i see what you mean but how do i have it "then assign each value to a different key" becuase you would have to have it count or something this is the part i'am having problems with then having it check thoses assigned number to see if match if it does then s/n has been used before so program won't run....

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

here is what i have so far only thing i have to added is code so that you can't run serial number twice...which i'am haveing problems with Sad

here is what i have so far Smile

also to notice i thought i would added something that would help make it hard to read ini file Smile

tim6389 · Professional Member Joined: 01 Aug 2002 Posts: 790

any tips on the above code to make it check for s/n so it can't run a "key" twice Smile

thanks

DW · Contributor Joined: 21 Mar 2003 Posts: 175 Location: UK

if the program blacklisted a number in reg or file, then the user would just have to delete the file or reg key.
maybe if there was a way to encript in into the exe, but then again the user could just reinstall it.

you could do a call home feature or something

Garrett · Posted: Fri Apr 04, 2003 9:00 pm Post subject:

Such security is really hard to make. My opinion is that if you can at
least protect your program from the common person trying to get by
your registration, then that is the best you can do.

Hackers and crackers will, one way or another defeat your security
no matter how hard you try to keep them from doing so.

-Garrett

DW · Contributor Joined: 21 Mar 2003 Posts: 175 Location: UK

i agree but today with all these tools and programs helping the common user do things they could only dream of, who knows, maybe the common user will be the biggest threat of them all.

an example
VDS turns what use to have to be done in a complex language into a simple easy to use language meaning anyone can write programs now not just programmers.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

Actually, DW, your idea of "call home" could be good. A system such as
requiring the user to register from a server would prevent bypassing the
registration system built into the program.

DW · Contributor Joined: 21 Mar 2003 Posts: 175 Location: UK

That would stop alot of user bypassing the reg system, but what about if someone finds a way to crack the app to use a local server, which would be another program on that same users machine, that simply does what the server does?

Call home systems are good, but they have there own work arounds. As does everything, but one other thing is the non internet user.
What about the people that want to use a program that have no net access?

Actually I just though of something, what if the program that called home also checked its own code for alterations?
I bet theres a way round that though too...

Security what a battle...
You know if the world wasnt based on greed and everything was free for the good of all we would have no problems security related or other. Everyone would be working on say something like windows or another big thing to make it better for the greater good, etc.
That would be nice, but it wont happen... Just a dream...