Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

An effective method for encrypting a license file?

Tags:

For a web application, I would like to create a simple but effective licensing system. In C#, this is a little difficult, since my decryption method could be viewed by anyone with Reflector installed.

What are some methods for encrypting files in C# that are fairly tamper-proof?

like image 927
David Brown Avatar asked Dec 11 '08 13:12

David Brown


People also ask

What are the 4 basic types of encryption systems?

While the most common are AES, RSA, and DES, there are other types being used as well. Let's dive into what these acronyms mean, what encryption is, and how to keep your online data safe.


1 Answers

It sounds like you want to be using Public/Private cryptography to sign a license token (an XML Fragment or file for example) so you can detect tampering. The simplest way to handle it is to do the following steps:

1) Generate a keypair for your company. You can do this in the Visual Studio command line using the SN tool. Syntax is:

sn -k c:\keypair.snk 

2) Use the keypair to strongly name (i.e. sign) your client application. You can set this using the signing tab in the properties page on your application

3) Create a license for your client, this should be an XML document and sign it using your Private key. This involves simply computing a digital signature and steps to accomplish it can be found at:

http://msdn.microsoft.com/en-us/library/ms229745.aspx

4) On the client, when checking the license you load the XmlDocument and use your Public key to verify the signature to prove the license has not been tampered with. Details on how to do this can be found at:

http://msdn.microsoft.com/en-us/library/ms229950.aspx

To get around key distribution (i.e. ensuring your client is using the correct public key) you can actually pull the public key from the signed assembly itself. Thus ensuring you dont have another key to distribute and even if someone tampers with the assembly the .net framework will die with a security exception because the strong name will no longer match the assembly itself.

To pull the public key from the client assembly you want to use code similar to:

    /// <summary>     /// Retrieves an RSA public key from a signed assembly     /// </summary>     /// <param name="assembly">Signed assembly to retrieve the key from</param>     /// <returns>RSA Crypto Service Provider initialised with the key from the assembly</returns>     public static RSACryptoServiceProvider GetPublicKeyFromAssembly(Assembly assembly)     {         if (assembly == null)             throw new ArgumentNullException("assembly", "Assembly may not be null");          byte[] pubkey = assembly.GetName().GetPublicKey();         if (pubkey.Length == 0)             throw new ArgumentException("No public key in assembly.");          RSAParameters rsaParams = EncryptionUtils.GetRSAParameters(pubkey);         RSACryptoServiceProvider rsa = new RSACryptoServiceProvider();         rsa.ImportParameters(rsaParams);          return rsa;     } 

I've uploaded a sample class with a lot of helpful Encryption Utilities on Snipt at: http://snipt.net/Wolfwyrd/encryption-utilities/ to help get you on your way.

I have also included a sample program at: https://snipt.net/Wolfwyrd/sign-and-verify-example/. The sample requires that you add it to a solution with the encryption utils library and provide a test XML file and a SNK file for signing. The project should be set to be signed with the SNK you generate. It demonstrates how to sign the test XML file using a private key from the SNK and then verify from the public key on the assembly.

Update

Added an up to date blog post with a nice detailed run through on license files

like image 56
Wolfwyrd Avatar answered Oct 05 '22 16:10

Wolfwyrd