Crypto: AES GCM
The AES GCM sample shows how to perform authenticated encryption and decryption operations using the GCM algorithm and a 128-bit key.
Requirements
The sample supports the following development kits:
Hardware platforms |
PCA |
Board name |
Build target |
|---|---|---|---|
PCA10095 |
|
||
PCA10095 |
|
||
PCA10090 |
|
||
PCA10090 |
|
||
PCA10056 |
|
When built for nrf5340dk_nrf5340_cpuapp_ns and nrf9160dk_nrf9160_ns targets, the sample is configured to compile and run as a non-secure application. Therefore, it automatically includes TF-M that prepares the required peripherals to be available for the application.
Overview
The sample performs the following operations:
Initialization:
The Platform Security Architecture (PSA) API is initialized.
A random AES key is generated and imported into the PSA crypto keystore.
Encryption and decryption of a sample plaintext:
A random initialization vector (IV) is generated.
Authenticated encryption is performed.
Authenticated decryption is performed.
Cleanup:
The AES key is removed from the PSA crypto keystore.
Building and running
This sample can be found under samples/crypto/aes_gcm 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.