1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright(c) 2018 Intel Corporation. 3 4Federal Information Processing Standards (FIPS) CryptoDev Validation 5==================================================================== 6 7Overview 8-------- 9 10Federal Information Processing Standards (FIPS) are publicly announced standards 11developed by the United States federal government for use in computer systems by 12non-military government agencies and government contractors. 13 14This application is used to parse and perform symmetric cryptography 15computation to the NIST Cryptographic Algorithm Validation Program (CAVP) and 16Automated Crypto Validation Protocol (ACVP) test vectors. 17 18For an algorithm implementation to be listed on a cryptographic module 19validation certificate as an Approved security function, the algorithm 20implementation must meet all the requirements of FIPS 140-2 (in case of CAVP) 21and FIPS 140-3 (in case of ACVP) and must successfully complete the 22cryptographic algorithm validation process. 23 24Limitations 25----------- 26 27CAVP 28---- 29 30* The version of request file supported is ``CAVS 21.0``. 31* If the header comment in a ``.req`` file does not contain a Algo tag 32 i.e ``AES,TDES,GCM`` you need to manually add it into the header comment for 33 example:: 34 35 # VARIABLE KEY - KAT for CBC / # TDES VARIABLE KEY - KAT for CBC 36 37* The application does not supply the test vectors. The user is expected to 38 obtain the test vector files from `CAVP 39 <https://csrc.nist.gov/projects/cryptographic-algorithm-validation- 40 program/block-ciphers>`_ website. To obtain the ``.req`` files you need to 41 email a person from the NIST website and pay for the ``.req`` files. 42 The ``.rsp`` files from the site can be used to validate and compare with 43 the ``.rsp`` files created by the FIPS application. 44 45* Supported test vectors 46 * AES-CBC (128,192,256) - GFSbox, KeySbox, MCT, MMT 47 * AES-GCM (128,192,256) - EncryptExtIV, Decrypt 48 * AES-CCM (128) - VADT, VNT, VPT, VTT, DVPT 49 * AES-CMAC (128) - Generate, Verify 50 * HMAC (SHA1, SHA224, SHA256, SHA384, SHA512) 51 * TDES-CBC (1 Key, 2 Keys, 3 Keys) - MMT, Monte, Permop, Subkey, Varkey, 52 VarText 53 54ACVP 55---- 56 57* The application does not supply the test vectors. The user is expected to 58 obtain the test vector files from `ACVP <https://pages.nist.gov/ACVP>`_ 59 website. 60* Supported test vectors 61 * AES-CBC (128,192,256) - AFT, MCT 62 * AES-GCM (128,192,256) - AFT 63 * AES-CMAC (128,192,256) - AFT 64 * AES-CTR (128,192,256) - AFT, CTR 65 * AES-GMAC (128,192,256) - AFT 66 * AES-XTS (128,256) - AFT 67 * HMAC (SHA1, SHA224, SHA256, SHA384, SHA512) 68 * SHA (1, 256, 384, 512) - AFT, MCT 69 * TDES-CBC - AFT, MCT 70 * TDES-ECB - AFT, MCT 71 * RSA 72 * ECDSA 73 74 75Application Information 76----------------------- 77 78If a ``.req`` is used as the input file after the application is finished 79running it will generate a response file or ``.rsp``. Differences between the 80two files are, the ``.req`` file has missing information for instance if doing 81encryption you will not have the cipher text and that will be generated in the 82response file. Also if doing decryption it will not have the plain text until it 83finished the work and in the response file it will be added onto the end of each 84operation. 85 86The application can be run with a ``.rsp`` file and what the outcome of that 87will be is it will add a extra line in the generated ``.rsp`` which should be 88the same as the ``.rsp`` used to run the application, this is useful for 89validating if the application has done the operation correctly. 90 91 92Compiling the Application 93------------------------- 94 95* Compile Application 96 97 To compile the sample application see :doc:`compiling`. 98 99* Run ``dos2unix`` on the request files 100 101 .. code-block:: console 102 103 dos2unix AES/req/* 104 dos2unix GCM/req/* 105 dos2unix CCM/req/* 106 dos2unix CMAC/req/* 107 dos2unix HMAC/req/* 108 dos2unix TDES/req/* 109 dos2unix SHA/req/* 110 111Running the Application 112----------------------- 113 114The application requires a number of command line options: 115 116 .. code-block:: console 117 118 ./dpdk-fips_validation [EAL options] 119 -- --req-file FILE_PATH/FOLDER_PATH 120 --rsp-file FILE_PATH/FOLDER_PATH 121 [--cryptodev DEVICE_NAME] [--cryptodev-id ID] [--path-is-folder] 122 --mbuf-dataroom DATAROOM_SIZE 123 124where, 125 * req-file: The path of the request file or folder, separated by 126 ``path-is-folder`` option. 127 128 * rsp-file: The path that the response file or folder is stored. separated by 129 ``path-is-folder`` option. 130 131 * cryptodev: The name of the target DPDK Crypto device to be validated. 132 133 * cryptodev-id: The id of the target DPDK Crypto device to be validated. 134 135 * path-is-folder: If presented the application expects req-file and rsp-file 136 are folder paths. 137 138 * mbuf-dataroom: By default the application creates mbuf pool with maximum 139 possible data room (65535 bytes). If the user wants to test scatter-gather 140 list feature of the PMD he or she may set this value to reduce the dataroom 141 size so that the input data may be divided into multiple chained mbufs. 142 143 144To run the application in linux environment to test one AES FIPS test data 145file for crypto_aesni_mb PMD, issue the command: 146 147.. code-block:: console 148 149 $ ./dpdk-fips_validation --vdev crypto_aesni_mb -- 150 --req-file /PATH/TO/REQUEST/FILE.req --rsp-file ./PATH/TO/RESPONSE/FILE.rsp 151 --cryptodev crypto_aesni_mb 152 153To run the application in linux environment to test all AES-GCM FIPS test 154data files in one folder for crypto_aesni_gcm PMD, issue the command: 155 156.. code-block:: console 157 158 $ ./dpdk-fips_validation --vdev crypto_aesni_gcm0 -- 159 --req-file /PATH/TO/REQUEST/FILE/FOLDER/ 160 --rsp-file ./PATH/TO/RESPONSE/FILE/FOLDER/ 161 --cryptodev-id 0 --path-is-folder 162