Crypto: HMAC
The HMAC sample shows how to generate a message authentication code using the HMAC algorithm and then verify it. The HMAC algorithm in this sample uses SHA-256.
Requirements
The sample supports the following development kits:
Hardware platforms |
PCA |
Board name |
Build target |
|---|---|---|---|
PCA10095 |
|
||
PCA10095 |
|
||
PCA10090 |
|
||
PCA10090 |
|
||
PCA10056 |
|
When built for the nrf5340dk_nrf5340_cpuapp_ns target, the sample is configured to compile and run as a non-secure application.
Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.
This is also valid for the nrf9160dk_nrf9160_ns build target, if the sample supports it.
Overview
The sample performs the following operations:
Initialization of the Platform Security Architecture (PSA) API.
Signing and verification of a sample plaintext:
A secret key is generated and imported into the PSA crypto keystore.
HMAC signing is performed.
HMAC verification is performed.
Cleanup:
The secret key is removed from the PSA crypto keystore.
Building and running
This sample can be found under samples/crypto/hmac in the nRF Connect SDK folder structure.
See Building and programming an application for information about how to build and program the application.
Testing
After programming the sample to your development kit, complete the following steps to test it:
Connect to the kit with a terminal emulator (for example, PuTTY). See How to connect with PuTTY for the required settings.
Compile and program the application.
Observe the logs from the application using an RTT Viewer or a terminal emulator.
Note
By default, the sample is configured to use both RTT and UART for logging. If you are using RTT, skip the first step of the testing procedure.