Crypto API overview

The Crypto API is a cryptography framework in the Linux^® kernel. It is dedicated to the parts of the kernel that deal with cryptography, such as IPsec and dm-crypt.

Framework purpose

The purpose of this article is to introduce the Crypto API framework:

• general information
• main component/stakeholders
• how to use the Crypto API
• use cases

The Crypto API framework mainly includes all popular hash and block ciphers (encryption) functions.

A hash is a string or number generated from a text string. The length of the resulting string or number is fixed and widely varies with small variations of the input. The best hashing algorithms are designed so that it is impossible to turn a hash back into its original string. Hashing is particularly useful to compare a value with a stored value. However it cannot store its plain representation for security reasons. This makes hashing an ideal solution to store passwords.

Encryption turns data into a series of unreadable characters which length is not fixed. The encrypted strings can reversed back into their original decrypted form if the right key is not provided. Encrypting a confidential file is a good way to prevent anyone from accessing its content.

Drivers for CRYP (block cipher), HASH (hash) and CRC (cyclic redundancy check) are integrated within the Crypto API kernel service.

System overview

文件:Cryptoapi.png

Crypto API

Description of the components

OpenSSL and dm-crypt are not part of the Crypto API framework but they are typical users of the Crypto API services.

From User space to hardware

• OpenSSL (User space)

OpenSSL is a software library supporting the TLS and SSL protocols as well as cryptographic functions. Openssl is available in OpenSTLinux distribution.

• dm-crypt (Kernel space)

dm-crypt is a kernel disk encryption subsystem. It is natively available in the standard Linux kernel.

• Cryptodev (Kernel space)

Cryptodev is a device driver which provides a general interface for userland applications. Although it is not part of the standard Linux kernel, it is available in OpenSTLinux distribution.

• CryptoAPI core (Kernel space)

This layer represents the standard Linux kernel cryptographic framework.

• hash, cryp and crc32 (Kernel space)

These are the cryptographic Linux drivers handling the HW blocks.

• HASH, CRYP and CRC (Hardware)

These HW blocks handle hash, ciphering, and CRC checksum.

API description

The Crypto API is documented in the Linux Kernel Crypto API section of the Linux Kernel documentation. It offers both a kernel and a userland interface:

• kernel internal interface, used in particular by dm-crypt.
• userland algorithm interface (socket) named AF_ALG. OpenSSL can use this interface.

In addition to the socket user interface, a more friendly interface, the cryptodev, can be used. It offers the /dev/crypto ioctl API. It is roughly described by the cryptodev.h header file. OpenSSL can be configured to use this interface as an alternative to the historical AF_ALG interface.

Configuration

Kernal configuration

The Crypto API is activated by default in ST deliveries. Nevertheless, if a specific configuration is required, you can use Linux Menuconfig tool: Menuconfig or how to configure kernel and select:

[*] Cryptographic API  --->
    [*]   Hardware crypto devices  --->
        [*]   Support for STM32 crc accelerators
        [*]   Support for STM32 hash accelerators
        [*]   Support for STM32 crypto accelerators

Devicetree configuration

By default the drivers are not enabled, so this needs to be added if you want to use HW accelerators.

• crc: CRC_device_tree_configuration.
• hash: HASH_device_tree_configuration.
• crypto: CRYP_device_tree_configuration.

How to use the Crypto API framework

The Crypto API framework can be used by other kernel modules.

The Crypto API documentation provides kernel code examples:

• Symmetric-key cipher operation.
• Operational state memory with SHASH.

Use cases

• Disk encryption

This is a typical example of Crypto API framework usage. Refer to LUKS for a standard disk encryption process.

How to trace and debug the framework

How to monitor

The list of available ciphers is given in /proc/crypto:

Board $> cat /proc/crypto

Output part showing that an STM32 driver provides with the CRC32 cipher:

...
name         : crc32
driver       : stm32-crc32
module       : kernel
priority     : 200
refcnt       : 1
selftest     : passed
internal     : no
type         : shash
blocksize    : 1
digestsize   : 4 
...

How to trace

There are no specific traces for this framework.

How to debug

There are no specific debug means for this framework.

Generic source code location

• crypto | |}} CryptoAPI core
• include/linux/crypto.h | |}} CryptoAPI interface
• drivers/crypto/stm32 | |}} stm32 crypto drivers

References

<securetransclude src="ProtectedTemplate:PublicationRequestId" params="7954 | 2018-06-29 | AnneJ"></securetransclude> <securetransclude src="ProtectedTemplate:ArticleBasedOnModel" params="Framework overview article model"></securetransclude> <securetransclude src="ProtectedTemplate:ReviewsComments" params="JCT 1840: alignment needed with the last version of the model"></securetransclude>{{#set:Has reviews comments=true}}