How to create an RSA key pair on Android to protect data

Abel Suviri Payán outlines the steps for creating an RSA key pair on Android for signing and verifying data.

How to create an RSA key pair on Android to protect data. Photo by Vojtech Bruzek on Unsplash.

In this post, I will explain how to create an RSA key pair on Android and use that key pair for sign and verify data. This RSA key pair will be stored in the Android KeyStore.

What is RSA?

RSA is a public-key or asymmetric crypto system. It uses a public key for encryption and a private key for decryption. Anyone can use the public key to encrypt a message, but it can be decrypted only by the private key owner.

What is the Android KeyStore?

The Android KeyStore is a storage facility for cryptographic keys and certificates. The keys stored in the KeyStore can be used for cryptographic operations, but the key material will not be extracted. This means an attacker might use a stored key, but will not be able to export it outside the device. When a key is created from an app and stored in the KeyStore, the access to the key will be restricted to the app itself.

Why use RSA?

We can use RSA to sign and verify data, for example when we transfer some data to a server. Because RSA is a public-key system, we can use the private key to sign data in our app and send the public key to the server, so the server can verify that the data sent is genuine and hasn’t been tampered with. If any malicious users know the public key, the only thing they can do is verify the integrity of the data, but they cannot change the data because they need the private key to do so.

We can use RSA to sign and verify data, for example when we transfer some data to a server. Image by Abel Suviri Payán.

Generate the key

To generate a new key, we have to create a KeyPairGenerator object. We have to specify the algorithm of the key we’re creating (in this case RSA), and the KeyStore where the key will be stored (in this case AndroidKeyStore).

We then create a KeyGenParameterSpec object to set all the parameters for our key. (Note that this class is available for Marshmallow and later versions. See KeyPairGeneratorSpec for older versions support.) It’s mandatory to set the key alias (name of the key) and the purpose for the key. If the purpose is sign, and we try to use the key to verify, it will throw an exception, so we have to know what we’re going to do with the keys – in this case, sign and verify. Other mandatory parameters are the digest and the signature padding (because we’re going to use the key to sign).

We can then set some optional parameters, such as the self-signed certificate serial number, the certificate subject (common name), the starting and expiry dates, and whether the key requires user authentication to be used.

Use the private key to sign data

To sign data, we have to retrieve the key from the KeyStore. First we have to request a KeyStore object and provide the type – AndroidKeyStore in this sample. We have to load an empty KeyStore, so we pass null as the InputStream argument in the load method.

Once the KeyStore has been loaded, we have to retrieve the private key, passing the alias (name) of the key we created earlier. Now we’re able to use the key to sign the data. It’s very important to set the algorithm when creating the Signature class instance. Because we’re using a RSA key with SHA256 message digest, we have to get this Signature object, otherwise it will throw an exception. The last step is to sign the data with our private key. We can encode and store the signature in a variable, as we need it for the verifying process.

Note that if the key requires authentication to be used, it will throw UserNotAuthenticatedException, so we have to ask the user to authenticate in this case.

Use the certificate to verify the signature

To verify the signature, we have to again load the KeyStore. Once the KeyStore is loaded, we have to retrieve our key certificate from there using our key alias. Finally, we create a Signature class instance passing the used algorithm as argument, and we verify that the signature matches our certificate.

If you have any suggestions or questions, please drop me a message! The full code for the sample is available here.

This article was reproduced in full with permission from the author. The original article was published on Medium, which you can find here.

Subscribe for more updates.

We process your personal data in accordance to our Privacy Policy.

Request a Call

Want to see Interact in action?
Click here to request a demo.

Request a Call

Top stories -

Debt Collections Technology -

Making a case for digitalising customer collections...

Kevin Phillips outlines the benefits of digitalisation in the customer collections process, achieving a win-win scenario...

Read more
Press releases -

ieDigital shortlisted for open banking and rebranding awards

ieDigital shortlisted in Excellence in Open Banking and Best Rebrand categories at Credit Awards 2019, as Credit...

Read more
Fintech Development -

Utility companies should collaborate to innovate

Digital transformation isn’t just about having a grasp on new technologies. It’s about knowing what your customer...

Read more