That's incorrect. To replace the public key, you have to modify the .exe or .dll (or in this case, .vst or .vst3.) This makes it a crack, because it's modifying the original file. At that point, it's easier for the cracking group to bypass the DRM entirely, instead of finding the signature checking code, but then leaving it intact and also replacing the public key. No cracking group would bother to do what you're describing, because it's more work than a normal crack, but for no benefit.lobanov wrote: Sat Oct 25, 2025 11:14 pmSorry for offtopic, but you are wrong. Signature cheking doesn't stop keygens at all and can be broken trivially. It is always possible (without additional checks) generate a new public and private keys pair, sign any user data and replace the public key used for checks.tumface wrote: Sat Oct 25, 2025 3:27 pm My preferred way is public+private serial key signature checking, like what FabFilter and REAPER use, which don't require activation checks. That method isn't as good at stopping key sharing amongst friends, but it does completely stop keygens.
I never said that public+private signature checks stops cracks. Nothing stops cracks.
