As @ArtjomB notes, you would keep the key safe by not putting it into your program. During startup, an authorized user or security device will need to provide the key. Anything that doesn't look like that is no longer encryption or security, it's some form of obfuscation. Obfuscation (or 'DRM') can be somewhere between useless and somewhat effective depending on how much effort you're going to put into it versus how much interest there is in cracking it. What's your ongoing budget for improving this as new attacks come along?

Windows

What is the sophistication of your expected attackers? Apple (as one example) controls their hardware, firmware, and OS very tightly, and has a team entirely devoted to constantly improving that. The iPhone is generally jailbroken within a few weeks to months after new releases. You should consider that the best case scenario for an attractive target.

Powerful Conversion Ability • Convert any format of PowerPoint presentation to video. Get It is ideal for showing presentations at trade shows, digital signage, in-store displays and portable devices as a video podcast. It can convert PowerPoint presentations to almost all popular video formats such as MPEG-1 - 2, AVI, MP4, WMV, MOV, 3GP and HD videos.

Crack

2-Key Cryptography - Cryptography Tutorial. Another way of encrypting data was needed: Two-Key. More practical encryption methods were needed. It’s been nearly three months since Edward Snowden started telling the world about the. But the latest disclosures, by the,, and are perhaps the most profound yet: the N.S.A. Mar 30, 2012 - We don't really know what's there unless we hack into the chip, because it's all kept secret. Secrecy of the encryption algorithm; secrecy of the keys; secrecy of the hardware. Just Google terms such as Irdeto 5 hacks, Sat Universe and MOSC. You Only Have 2 Days To Grab The Samsung Galaxy S10.

If you're thinking 'well, what can I put together in an afternoon that will stop the ankle biters?' Do whatever comes to mind. XOR it with some other hard-coded value.

Maybe bitshift it or whatever. It won't help very much against anyone who cares, but it'll stop the most casual attacker, and at least you won't waste a ton of time and money on it. Stepping up from that, look at your platform's built-in solutions. OS assistance is a big help. In particular, look at on Windows. Mac provides licensing enforcement if you work through Mac App Store. Or you can look at commercial vendors like eSellerate who have their own proprietary solutions.

Of course all of these can be (and regularly are) defeated. But they're much stronger than whatever you're going to develop over a few days. Any specific approach you get off of StackOverflow will be, by definition, useless.

The only thing obfuscation has going for it is that its details are secret. If you know how it works, then you can beat it. That's what differentiates it from encryption. Good encryption is designed to be just as strong even if the attacker knows the entire algorithm. That's why obfuscation techniques are proprietary. They pretty much have to be.