Protection like IGloader but simpler

Miscellaneous Forums/General Discussion/Protection like IGloader but simpler

Has anyone seen this IGloader quote:

Integrated DRM
The integrated DRM (Digital Rights Management) protects your applications from unauthorised copying and launches. igLoader encrypts your .exe files in such a way that it is not possible to launch the software locally, the software must be launched through igLoader and through the correct website for it to function. This functionality makes igLoader ideal in situations where games are made available to play through subscription or credit based websites. It also ensures the client visits your website to play thus increasing customer retention and advertising potentials.

wouldnt it be possible to use BMAX for this sort of thing, Im thinking of doing it for one program im going to release next year.

It might go like this: you download the executable (only 300K-bytes) ,you run it, the executable connects to my site to get permission to run, then after passing it runs.

IGloader cost $590.00 a year for one program (half price after first year) so its kinda expensive for a hobbyist.

Generated ad revenue is said to cover a great portion of that at present.

It might go like this: you download the executable (only 300K-bytes) ,you run it, the executable connects to my site to get permission to run, then after passing it runs.


No reason why you couldn't do that... of course, any protection that hinges on a simple yes/no question can always be bypassed by a determined cracker, simply revert the yes/no branch in the compiled executable

You're going to have a number of issues:

1) Getting past a firewall
2) Guaranteeing the "License Server" is available
3) Dealing with Connection downtime
4) Locking the file down in such a way that it's impossible to run without the wrapper/code.
5) Launching the decrypted file -Where you gonna put it? Back to disk (RealArcade)? Launch from memory (igLoader).

PS. If IG is too expensive for you then come talk to me.

my site will be online just like this one! 24/7
Connection downtime this year 0 minutes! thats why we have raid arrays and Multi-processor servers and such!
I have no intention on putting a guarantee of any kind with my software, so no need to guarantee anything!
Locking down the file? the file is just a bunch of dead bytes without my connection.
Launching decrypted file? no need its an executable!
If your fire wall is blocking it, unblock it, I cant write software to unblock files from firewalls, give permission yourself manually! and If your firewall doesnot allow programs to be unblocked, what was the name of that firewall?

And I can use a "jit" (just in time compiler) so I can do things with that, kinda like a data file can contain executable code if I desire.

All answered, you where wrong sorry!

xlsior -

of course it wouldnt run by a simple yes/no, It would involve the visitors IP and remote address and an encrypted password only valid for that session.

It will also involve a feedback form and a blocking list for people who get nasty when they take drugs and say nasty stuff get blocked and they have nothing but a blank executable at there end that is completely useless and just exits back to windows.

And because they said in the feedback form that they hate my software they will be blocked and wont even get back into my site at all!

Of course it wouldn't run by a simple yes/no, It would involve the visitors IP and remote address and an encrypted password only valid for that session


...But in the end, somewhere in your program, you do your verification magic and have an "if blahblahblah all checks out then "yes, run it", else "don't run it". Still a matter of simply overwriting a couple of bytes in the .EXE to change the behavious to "if everything checks out then fail, otherwise run."

Also, be careful with the blocking based on IP -- many ISP's use proxy servers, meaning that web requests get routed through a server on the ISP's side first, and then passed along to yours. That means that the IP that your website sees, is not the actual user IP. If you block this IP from running, you will automatically block *every* user routed through the same proxy server, which in the case of the large ISP's like AOL, Earthlink, etc. can potentially mean millions of people. So... Blocking one 'wrong' IP because of a single bad user could mean that a million other people won't be able to run your program either. your call of course, but just be aware of the potential for problems once you start doing that.