- Introduction
- License
- Requirements
- Installation Instructions
- Examples
- Troubleshooting
- Loading Engines by Setting the OpenSSL Configuration File
- Contribution guidelines
- More Information
- Copyright
Kunpeng Accelerator Engine is to build performance competitiveness of common software libraries on the Kunpeng platform.
Kunpeng Accelerator Engine is a new technology within Hisilicon Kunpeng 920 processors which
provides a hardware-enabled foundation for security, authentication, and compression. It significantly increases the performance across cloud, networking, big data, and storage applications and platforms.
Kunpeng Accelerator Engine includes symmetric encryption, asymmetric encryption, digital signatures, and RSA for accelerating SSL/TLS application, which makes processors more efficient and reduces hardware costs. By accelerating SSL/TLS with Kunpeng Accelerator Engine, you can:
- Support higher-performance secured tunnels and a greater number of authenticated clients
- Have higher-performance encrypted traffic throughout a secured network
- Accelerate compute-intense symmetric and asymmetric cryptography
- Have greater platform application efficiency
- Have higher-performance compression and decompression
- Maximize CPU utilization
So far, the algorithms supported by Kunpeng Accelerator Engine are:
- Asymmetric encryption algorithm: RSA Support Key Sizes 1024/2048/3072/4096
- Digest algorithm: SM3/MD5
- Block cipher algorithm: SM4 Support CTR/XTS/CBC/ECB/OFB
- Block cipher algorithm: AES Support CTR/XTS/CBC/ECB
- Key exchange algorithm: DH Support 768bit/1024bit/1536bit/2048bit/3072bit/4096bit
It is licensed under the APACHE LICENSE, VERSION 2.0. For more information, see the LICENSE file.
- CPU: Kunpeng 920
- Operating System:
- CentOS 7.6 4.14.0-115.el7a.0.1.aarch64 version
- SuSE 15.1 4.12.14-195-default arch64 version
- NeoKylin 7.6 4.14.0-115.5.1.el7a.06.aarch64 version
- EulerOS 2.8 4.19.36-vhulk1907.1.0.h410.eulerosv2r8.aarch64 version
- BCLinux-R7-U6-Server-aarch64 version
- Kylin 4.0.2 (juniper) 4.15.0-70-generic version
- Kylin release 4.0.2 (SP2) 4.19.36-vhulk1907.1.0.h403.ky4.aarch64 version
- UniKylin Linux release 3(Core) 4.18.0-80.ky3.kb21.hw.aarch64 version
- Ubuntu 18.04.1 LTS 4.15.0-29-generic version
- OpenSSL 1.1.1a or later OpenSSL
Clone OpenSSL from Github at the following location:
git clone https://github.com/openssl/openssl.git
You are advised to check out and build the OpenSSL 1.1.1a git tag specified in the release notes. Versions of OpenSSL before OpenSSL 1.1.0 are not supported.
Note: You are not advised to install the accelerated version of OpenSSL as your default system library. Otherwise, acceleration may be used unexpectedly by other applications on the system, resulting in undesired/unsupported behavior. The --prefix
can be used with the ./config
command to specify the location that make install
will copy files to. Please see the OpenSSL INSTALL file for full details on usage of the --prefix
option.
By default, we usually install OpenSSL as follows:
./config -Wl,-rpath=/usr/local/lib
make
make install
The -Wl,-rpath
option can specify the openssl shared libraries where the binaries will link to.
Clone the Github repository containing the Kunpeng Accelerator Engine:
git clone https://github.com/kunpengcompute/KAE
Download the release version of Kunpeng Accelerator Engine Driver from:
https://github.com/kunpengcompute/KAEdriver/releases
Firstly, build and install the accelerator driver:
Note: To build the Kunpeng Accelerator Engine Driver, install the kernel-devel
package first.
tar -zxf Kunpeng_KAE_driver.tar.gz
cd kae_driver
make
make install
modprobe uacce
modprobe hisi_qm
modprobe hisi_sec2
modprobe hisi_hpre
modprobe hisi_zip
modprobe hisi_rde
Secondly, install the accelerator library:
cd warpdrive
sh autogen.sh
./configure
make
make install
Then, install the Kunpeng Accelerator Engine:
cd KAE
./configure
make
make install
Note: The --openssl_path
can be used with the ./configure
command to specify the location that make install
will copy files to. The default installation path for the accelerator engine is /usr/local/lib/openssl-1.1
. You are advised to install the Kunpeng Accelerator Engine as a default OpenSSL engine.
Export the environment variableas OPENSSL_ENGINES
as follows :
export OPENSSL_ENGINES=/usr/local/lib/engines-1.1
for more install guid and user guid, get information at: https://www.huaweicloud.com/kunpeng/software/accelerator.html
Run the following command to check when the Kunpeng Accelerator Engine is loaded correctly:
cd /usr/local/bin/
./openssl genrsa -out test.key -engine kae 2048
./openssl rsa -in test.key -pubout -out test_pub.key -engine kae
./openssl rsautl -encrypt -in rsa_test -inkey test_pub.key -pubin -out rsa_test.en -engine kae
./openssl rsautl -decrypt -in rsa_test.en -inkey test.key -out rsa_test.de -engine kae
./openssl enc -sm4-cbc -a -in sm4_test -out sm4_test.en -pass pass:123456 -engine kae
./openssl enc -sm4-cbc -a -in sm4_test -out sm4_test.en -pass pass:123456 -p -engine kae
./openssl enc -sm4-cbc -d -a -in sm4_test.en -out sm4_test.de -pass pass:123456 -engine kae
./openssl sm3 -out sm3_out -engine kae sm3_test
Here is an example to show you how to use the Kunpeng Accelerator Engine.
#include <stdio.h>
#include <stdlib.h>
/* OpenSSL headers */
#include <openssl/bio.h>
#include <openssl/err.h>
#include <openssl/engine.h>
int main(int argc, char **argv)
{
/* Initializing OpenSSL */
ERR_load_BIO_strings();
OpenSSL_add_all_algorithms();
/* You can use ENGINE_by_id Function to get the handle of the Kunpeng Accelerator Engine */
ENGINE *e = ENGINE_by_id("kae");
ENGINE_init(e);
/* Set the default RSA algorithms computed by KAE engine, more usage methods about ENGINE_set_default, please refer to OpenSSL official website */
ENGINE_set_default_RSA(e);
/*The user code To Do */
...
ENGINE_free(e);
}
The most likely failure point is that the Kunpeng Accelerator Engine is not loaded successfully. If this occurs:
-
Check that the accelerator driver has been loaded successfully by running the
lsmod
command.uacce.ko, hisi_qm.ko, sgl.ko, hisi_sec2.ko, hisi_hpre.ko, hisi_zip.ko
should be in the list. -
Check that the paths have been set correctly so that the
libkae.so
engine file can be copied to the correct location. -
Check that the installation path has been correctly added to the environment variable
OPENSSL_ENGINES
and exported to the shell by running theexport
command.
By setting up the OpenSSL configuration file, you can also initialize the Kunpeng Accelerator Engine for your OpenSSL application. For further details on using the openssl.cnf
file, see the OpenSSL online documentation at:
https://www.openssl.org/docs/man1.1.0/apps/config.html
Here is an example to show you how to set up the openssl.cnf
file to load engines. Add the following statements to the global section (assuming that the path is the one that KAE installed):
openssl_conf = openssl_engine_init
[ openssl_engine_init ]
engines = engine_section
[ engine_section ]
kae = kae_section
[ kae_section ]
engine_id = kae
dynamic_path = /usr/local/lib/engines-1.1/kae.so
Export the environment variableas OPENSSL_CONF
as follows :
export OPENSSL_CONF=/home/app/openssl.cnf
By loading the openssl configuration file, the user application does not need to modify any code, except for loading KAE through the following API during initialization.
OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL);
If you want to contribute to KAE, please use GitHub issues for tracking requests and bugs.
For further assistance and QA, contact Huawei Support at:
https://www.huaweicloud.com/kunpeng/software/accelerator.html
Copyright © 2018 Huawei Corporation. All rights reserved.