Differences
This shows you the differences between two versions of the page.
|
smd:laboratoare:08 [2020/04/14 22:44] vasile.cosovanu [Application signing] Updated steps |
smd:laboratoare:08 [2021/05/13 19:51] (current) adriana.draghici [Lab 8 - Cryptography 2] |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| * Protect the app's APK using signing | * Protect the app's APK using signing | ||
| * Use Android's KeyStore to generate and store cryptographic keys and use them to sign an app | * Use Android's KeyStore to generate and store cryptographic keys and use them to sign an app | ||
| - | * Verify message integrity using HMAC(hash-based message authentication code) | + | * Verify message integrity using HMAC (hash-based message authentication code) |
| * generate HMAC to sign a message | * generate HMAC to sign a message | ||
| * verify HMAC to check that the received message was not modified | * verify HMAC to check that the received message was not modified | ||
| Line 10: | Line 10: | ||
| ===== Application signing ===== | ===== Application signing ===== | ||
| - | If you want to install an application on Android, the //apk// must be digitally signed with a certificate. For example, when you test your application on the emulator, Android Studio signs the apk with a debug certificate. The first time when you run or [[https://developer.android.com/studio/publish/app-signing#debug-mode|debug a project in Android Studio]], a debug keystore and certificate is automatically created using the Android SDK tools in **$HOME/.android/debug.keystore**. Also the keystore is initialized and the key password are set. | + | If you want to install an application on Android, the //apk// must be digitally signed with a certificate. For example, when you test your application on the emulator, Android Studio signs the apk with a debug certificate. The first time when you run or [[https://developer.android.com/studio/publish/app-signing#debug-mode|debug a project in Android Studio]], a debug keystore and certificate is automatically created using the Android SDK tools in **$HOME/.android/debug.keystore**. Also the keystore is initialized and the key password is set. |
| As a security measure the debug certificate needs to be used only for testing and for debug builds. This certificate is not secure for using on app stores. | As a security measure the debug certificate needs to be used only for testing and for debug builds. This certificate is not secure for using on app stores. | ||
| Line 22: | Line 22: | ||
| - Complete the fields and then continue with the signing steps below | - Complete the fields and then continue with the signing steps below | ||
| | | ||
| - | From here we continue to sign the app with the key stored in the newly created keystore. You can skip the first to steps if you are already in the window at the 3rd step: | + | From here we continue to sign the app with the key stored in the newly created keystore. You can skip the first two steps if you are already in the window at the 3rd step: |
| - **Build -> Generate Signed Bundle/APK** | - **Build -> Generate Signed Bundle/APK** | ||
| - In the **Generate Signed Bundle/APK** choose **APK** | - In the **Generate Signed Bundle/APK** choose **APK** | ||
| Line 49: | Line 49: | ||
| In this task will create a signing configuration for different build types. | In this task will create a signing configuration for different build types. | ||
| - Create a release signing configuration with the data from Task 1. [[https://developer.android.com/studio/publish/app-signing#sign-auto|Auto sign]] | - Create a release signing configuration with the data from Task 1. [[https://developer.android.com/studio/publish/app-signing#sign-auto|Auto sign]] | ||
| - | - Build a release version when pressing Run. Check **Build Variants** view from Android Studio. | + | - Build a release version when pressing Run. Check **Build** -> **Select Build Variant** view from Android Studio. |
| - Create a release signing configuration using a new key. | - Create a release signing configuration using a new key. | ||
| - Sign the application wth the new release config and use adb to install the signed apk. You should install the new signed apk on top of the one from item #2. What happens with the application? | - Sign the application wth the new release config and use adb to install the signed apk. You should install the new signed apk on top of the one from item #2. What happens with the application? | ||
| Line 55: | Line 55: | ||
| ==== Task 3 - Generate and Verify HMAC (4p) ==== | ==== Task 3 - Generate and Verify HMAC (4p) ==== | ||
| + | |||
| + | <note tip> | ||
| + | Hash-based message authentication code (HMAC) is a mechanism for verifying the authenticity and integrity of a message. | ||
| + | You can compute it using a hashing crypto algorithm (e.g. SHA-2 family HMAC) and a secret symmetric key. In Android you can use the standard Java API (javax.crypto) for computing it. | ||
| + | </note> | ||
| Add an activity to the project. Include an **EditText** and a **Button** in the first activity. When the user types a text and presses the button, it will send the text to the second activity through an intent (**putExtra**). In the second activity, get the message from the Intent and display it in the **TextView**. | Add an activity to the project. Include an **EditText** and a **Button** in the first activity. When the user types a text and presses the button, it will send the text to the second activity through an intent (**putExtra**). In the second activity, get the message from the Intent and display it in the **TextView**. | ||
| Line 60: | Line 65: | ||
| In the first activity generate a symmetric key using [[https://developer.android.com/reference/javax/crypto/KeyGenerator|KeyGenerator]] for //HmacSha256// algorithm. Save this key in a Singleton (that can be accessed from both activities). Then generate the HMAC of the text introduced by the user (using [[https://developer.android.com/reference/javax/crypto/Mac.html|MAC]] with HmacSha256 algorithm) and send the HMAC along with the initial message (through the Intent). In the second activity, obtain the HMAC from the Intent, obtain the Singleton, get the symmetric key and recompute the HMAC. If the HMAC is valid (equal with the recomputed one), Display the message "Data is unmodified". | In the first activity generate a symmetric key using [[https://developer.android.com/reference/javax/crypto/KeyGenerator|KeyGenerator]] for //HmacSha256// algorithm. Save this key in a Singleton (that can be accessed from both activities). Then generate the HMAC of the text introduced by the user (using [[https://developer.android.com/reference/javax/crypto/Mac.html|MAC]] with HmacSha256 algorithm) and send the HMAC along with the initial message (through the Intent). In the second activity, obtain the HMAC from the Intent, obtain the Singleton, get the symmetric key and recompute the HMAC. If the HMAC is valid (equal with the recomputed one), Display the message "Data is unmodified". | ||
| - | Hint: Send data and HMAC as byte arrays in the Intent.\\ | + | Send the data and HMAC as byte arrays in the Intent. Use Arrays.equals() for byte arrays comparison. |
| - | Hint: Use Arrays.equals() for byte arrays comparison.\\ | + | |
| + | <code Java> | ||
| + | String secret = "secret"; | ||
| + | String message = "important message"; | ||
| + | |||
| + | Mac sha256HMAC = Mac.getInstance("HmacSHA256"); | ||
| + | SecretKeySpec secretKey = new SecretKeySpec(secret.getBytes(),"HmacSHA256"); | ||
| + | sha256HMAC.init(secretkey); | ||
| + | byte[] secretMessageBytes = sha256HMAC.doFinal(message.getBytes()) | ||
| + | </code> | ||
| + | |||
| + | |||
| ==== Useful Links ==== | ==== Useful Links ==== | ||
