So, with that out of the way, I have working sources already available for Widowmaker SDK. If you directly compile them INTO their individual binaries without actually going through and altering the code as necessary, then you're going to run into a lot of problems. The second part comes the ftp server. I have my own, but I'm not going to hand out FTP accounts. You want to see it work, email me info, and I'll have a working example within less than 8 hours of reading/responding. The only
Windows 10 minimum requirements are basically a 1GHz processor and 1GB of RAM.
Tell them to fuck off, or change the name of the application.
They got in through the backdoor.
They say once you develop a taste for long pig, it never goes away.
It's actually about 6 years old. Eventually, I'll get around to changing it to a different theme/style.
I understand why you'd want the cake without having to bake it. I get that, I really do. But the point is, IDGAF either way. I'm not the one wanting the pre-baked cake, and if I did, much like yourself, I'd go to the store and buy one. If someone wants me to bake that cake for them, well, cough up some cash and make the adventure worth my time.
If they do, then there's a bigger problem to worry about, and it's not DRM.
The whole point of the recipe is for the developer to make the cake. That's what software development is. As for the padlock metaphor NOTHING is crackproof, and I never claimed that it was anyway.
That goes without saying.
Also, they would need to know the following 1) Another client's hardware ID 2) location of every module/software they plan on downloading while directory views on the server are disabled. The cracking part is a lot easier said than done.
They call said company, give them the old hardware ID code, then the new hardware ID code. From there, the administrative side takes less than 5 minutes to do, which the old profile is copied to the new server-side hardware identifier, and the appropriate adjustments are made to the encrypted profile. They restart the application, and the software automagically works. As I said earlier, a 5 year old could do it.
There doesn't need to be, but in order for that to actually work, you have to know the exact make of another user's computer, along with the resulting hardware ID code. It can be done, but it's not as easy as you think.
Less than 2 years ago*