Hackers would then use this logic to create keygens that could produce fake serial numbers that these apps would naively accept as being legitimate. In fact, decompilers like Hopper nowadays are so good that they can even convert the decompiled assembly code into a pretty readable pseudo C code, making it pretty easy to figure out how an app works. The validation logic was often some sort of hash function that was calculated on top of the serial number, and because this all happened offline, it wasn't very hard for a hacker to decompile the software and find out what this logic was. However, serial numbers at the time were also very flawed. In the mid-2000s, serial numbers were a very common way to validate purchases, and every software/game you bought from a store would come with a serial number in the box which you had to input when installing it to prove that you were in possession of a legitimate copy of the software. But how do you know the code is legitimate? Is it possible to confirm that the code was 100%, without a shadow of a doubt, provided by you, and not faked by someone who reverse-engineered the logic? Serial numbers in the past In these cases, you'll have to ship your own licensing system that is capable of validating and upgrading an instance of the app.Ī simple way to achieve this is to provide serial numbers - a system in which a user of the app can purchase one of these numbers and input it into the app to unlock its premium features. The easiest alternative is this case is to add an in-app purchase for the pro version, but for macOS apps, you might want to not use the App Store at all. If what you're developing is an offline productivity tool, then you might not have a backend at all. The safest way to include a "pro" version in your app is to have a backend that is capable of providing content to premium users, but not every app falls into this category.
0 kommentar(er)
