/openbmc/linux/arch/arm64/crypto/ |
H A D | Kconfig | 13 GCM GHASH function (NIST SP800-38D) 162 - ECB (Electronic Codebook) mode (NIST SP800-38A) 163 - CBC (Cipher Block Chaining) mode (NIST SP800-38A) 164 - CTR (Counter) mode (NIST SP800-38A) 165 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E 179 - ECB (Electronic Codebook) mode (NIST SP800-38A) 180 - CBC (Cipher Block Chaining) mode (NIST SP800-38A) 181 - CTR (Counter) mode (NIST SP800-38A) 182 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E 210 - ECB (Electronic Codebook) mode (NIST SP800-38A) [all …]
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | NIST-Software | 1 NIST-developed software is provided by NIST as a public service. 11 NIST-developed software is expressly provided "AS IS." NIST MAKES NO 14 FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND DATA ACCURACY. NIST 16 UNINTERRUPTED OR ERROR-FREE, OR THAT ANY DEFECTS WILL BE CORRECTED. NIST DOES 27 property. The software developed by NIST employees is not subject to copyright
|
H A D | NIST-PD | 4 and Technology (NIST), and others. This software has been contributed to the 6 NIST employees are not subject to copyright protection in the United States and 10 This software is provided "AS IS." NIST MAKES NO WARRANTY OF ANY KIND, EXPRESS, 13 ACCURACY. NIST does not warrant or make any representations regarding the use
|
H A D | NIST-PD-fallback | 3 …NIST), an agency of the Federal Government and is being made available as a public service. Pursua… 5 …, OR ANY WARRANTY THAT THE SOFTWARE WILL BE ERROR FREE. IN NO EVENT SHALL NIST BE LIABLE FOR ANY D…
|
/openbmc/linux/arch/arm/crypto/ |
H A D | Kconfig | 25 GCM GHASH function (NIST SP800-38D) 177 - ECB (Electronic Codebook) mode (NIST SP800-38A) 178 - CBC (Cipher Block Chaining) mode (NIST SP800-38A) 179 - CTR (Counter) mode (NIST SP800-38A) 180 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E 198 - ECB (Electronic Codebook) mode (NIST SP800-38A) 199 - CBC (Cipher Block Chaining) mode (NIST SP800-38A) 200 - CTR (Counter) mode (NIST SP800-38A) 201 - CTS (Cipher Text Stealing) mode (NIST SP800-38A) 202 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
|
/openbmc/linux/crypto/ |
H A D | ecdsa.c | 112 /* faster alternative for NIST p384, p256 & p192 */ in _ecdsa_verify() 273 .cra_name = "ecdsa-nist-p384", 274 .cra_driver_name = "ecdsa-nist-p384-generic", 295 .cra_name = "ecdsa-nist-p256", 296 .cra_driver_name = "ecdsa-nist-p256-generic", 317 .cra_name = "ecdsa-nist-p192", 318 .cra_driver_name = "ecdsa-nist-p192-generic", 330 /* NIST p192 may not be available in FIPS mode */ in ecdsa_init() 367 MODULE_ALIAS_CRYPTO("ecdsa-nist-p192"); 368 MODULE_ALIAS_CRYPTO("ecdsa-nist-p256"); [all …]
|
H A D | ecdh.c | 145 .cra_name = "ecdh-nist-p192", 146 .cra_driver_name = "ecdh-nist-p192-generic", 170 .cra_name = "ecdh-nist-p256", 171 .cra_driver_name = "ecdh-nist-p256-generic", 195 .cra_name = "ecdh-nist-p384", 196 .cra_driver_name = "ecdh-nist-p384-generic", 209 /* NIST p192 will fail to register in FIPS mode */ in ecdh_init()
|
H A D | Kconfig | 659 CBC (Cipher Block Chaining) mode (NIST SP800-38A) 668 CFB (Cipher Feedback) mode (NIST SP800-38A) 677 CTR (Counter) mode (NIST SP800-38A) 684 CBC-CS3 variant of CTS (Cipher Text Stealing) (NIST 695 ECB (Electronic Codebook) mode (NIST SP800-38A) 717 KW (AES Key Wrap) authenticated encryption mode (NIST SP800-38F 742 OFB (Output Feedback) mode (NIST SP800-38A) 778 XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E 829 authenticated encryption mode (NIST SP800-38C) 840 (GCM Message Authentication Code) (NIST SP800-38D) [all …]
|
H A D | ecc_curve_defs.h | 5 /* NIST P-192: a = p - 3 */ 31 /* NIST P-256: a = p - 3 */ 57 /* NIST P-384 */
|
H A D | ghash-generic.c | 18 * However, the NIST standard for GCM [2] presents GHASH as GHASH(H, X) where X 34 * (https://csrc.nist.gov/publications/detail/sp/800-38d/final)
|
/openbmc/openbmc/poky/meta/conf/distro/include/ |
H A D | cve-extra-exclusions.inc | 18 # strace https://nvd.nist.gov/vuln/detail/CVE-2000-0006 22 # epiphany https://nvd.nist.gov/vuln/detail/CVE-2005-0238 30 # glibc https://nvd.nist.gov/vuln/detail/CVE-2010-4756 37 # go https://nvd.nist.gov/vuln/detail/CVE-2020-29509 38 # go https://nvd.nist.gov/vuln/detail/CVE-2020-29511 68 # qemu:qemu-native:qemu-system-native https://nvd.nist.gov/vuln/detail/CVE-2021-20255 74 # qemu:qemu-native:qemu-system-native https://nvd.nist.gov/vuln/detail/CVE-2019-12067 80 # nasm:nasm-native https://nvd.nist.gov/vuln/detail/CVE-2020-18974
|
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-bsp/images/npcm7xx-igps-native/ |
H A D | BootBlockAndHeader_GBS.xml | 160 0x02: SECURITY_LEVEL_NIST. (require BootBlock with NIST support) --> 189 <!-- hole 0 size: used for NIST security. --> 200 <!-- hole 0: used for NIST security. --> 209 <!-- hole 0 size: used for NIST security. --> 219 <!-- hole 1: used for NIST security. --> 228 <!-- hole 1 size: used for NIST security. --> 239 <!-- hole 2: used for NIST security. --> 248 <!-- hole 2 size: used for NIST security. --> 258 <!-- hole 3: used for NIST security. --> 267 <!-- hole 3 size: used for NIST security. -->
|
/openbmc/docs/designs/ |
H A D | redfish-resource-supplement-for-pfr.md | 13 NIST SP 800-193 provides technical guidelines and recommendations supporting 27 Platform Firmware Resilience technology in NIST SP 800-93 provide common 35 - [NIST.SP.180-193](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-193.pdf) 51 Resilience by using guidelines provided by NIST SP 800-193. Some of the
|
/openbmc/qemu/tests/unit/ |
H A D | test-crypto-cipher.c | 40 * http://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf 44 /* NIST F.1.1 ECB-AES128.Encrypt */ 61 /* NIST F.1.3 ECB-AES192.Encrypt */ 78 /* NIST F.1.5 ECB-AES256.Encrypt */ 97 /* NIST F.2.1 CBC-AES128.Encrypt */ 115 /* NIST F.2.3 CBC-AES128.Encrypt */ 133 /* NIST F.2.5 CBC-AES128.Encrypt */ 538 /* NIST F.5.1 CTR-AES128.Encrypt */ 556 /* NIST F.5.3 CTR-AES192.Encrypt */ 574 /* NIST F.5.5 CTR-AES256.Encrypt */
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Key_v1.xml | 103 <Annotation Term="OData.Description" String="NIST P-256."/> 107 <Annotation Term="OData.Description" String="NIST P-384."/> 111 <Annotation Term="OData.Description" String="NIST P-521."/> 115 <Annotation Term="OData.Description" String="NIST K-163."/> 119 <Annotation Term="OData.Description" String="NIST P-192."/> 123 <Annotation Term="OData.Description" String="NIST P-224."/> 127 <Annotation Term="OData.Description" String="NIST K-233."/> 131 <Annotation Term="OData.Description" String="NIST B-233."/> 135 <Annotation Term="OData.Description" String="NIST K-283."/> 139 <Annotation Term="OData.Description" String="NIST K-409."/> [all …]
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | vulnerabilities.rst | 79 MORE INFORMATION: https://nvd.nist.gov/vuln/detail/CVE-2016-6354 90 MORE INFORMATION: https://nvd.nist.gov/vuln/detail/CVE-2019-6293 114 upstream `NIST CVE database <https://nvd.nist.gov/>`__. 131 NVD about CVE entries can be provided through the `NVD contact form <https://nvd.nist.gov/info/cont… 261 Then, the code looks up all the CVE IDs in the NIST database for all the 285 - study the latest information in `CVE database <https://nvd.nist.gov/vuln/search>`__.
|
/openbmc/linux/Documentation/devicetree/bindings/crypto/ |
H A D | intel,keembay-ocs-ecc.yaml | 16 cryptography using the NIST P-256 and NIST P-384 elliptic curves.
|
/openbmc/openbmc/poky/meta/recipes-core/glibc/ |
H A D | glibc_2.40.bb | 4 # glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-1010022 5 # glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-1010023 6 # glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-1010024 13 # glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-1010025
|
/openbmc/linux/drivers/crypto/intel/keembay/ |
H A D | keembay-ocs-ecc.c | 509 * The maximum security strength identified by NIST SP800-57pt1r4 for in kmb_ecc_gen_privkey() 832 .cra_name = "ecdh-nist-p256", 833 .cra_driver_name = "ecdh-nist-p256-keembay-ocs", 849 .cra_name = "ecdh-nist-p384", 850 .cra_driver_name = "ecdh-nist-p384-keembay-ocs", 1006 MODULE_ALIAS_CRYPTO("ecdh-nist-p256"); 1007 MODULE_ALIAS_CRYPTO("ecdh-nist-p384"); 1008 MODULE_ALIAS_CRYPTO("ecdh-nist-p256-keembay-ocs"); 1009 MODULE_ALIAS_CRYPTO("ecdh-nist-p384-keembay-ocs");
|
/openbmc/linux/fs/udf/ |
H A D | udftime.c | 19 * For more NIST information (especially dealing with leap seconds), see: 20 * http://www.boulder.nist.gov/timefreq/pubs/bulletin/leapsecond.htm
|
/openbmc/u-boot/include/u-boot/ |
H A D | sha1.h | 10 * The SHA-1 standard was published by NIST in 1993. 12 * http://www.itl.nist.gov/fipspubs/fip180-1.htm
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PFR/ |
H A D | Attributes.interface.yaml | 3 recommended by NIST SP 800-193.
|
/openbmc/linux/drivers/crypto/ |
H A D | atmel-ecc.c | 107 * The device only supports NIST P256 ECC keys. The public key size will in atmel_ecdh_set_secret() 290 * The device only supports NIST P256 ECC keys. The public key size will in atmel_ecdh_max_size() 306 .cra_name = "ecdh-nist-p256",
|
/openbmc/openbmc/poky/meta/recipes-core/meta/ |
H A D | cve-update-nvd2-native.bb | 17 NVDCVE_URL ?= "https://services.nvd.nist.gov/rest/json/cves/2.0" 19 # If you have a NVD API key (https://nvd.nist.gov/developers/request-an-api-key) 142 NVD API documentation: https://nvd.nist.gov/developers/vulnerabilities
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libtar/files/ |
H A D | CVE-2013-4420.patch | 6 Description of the vulnerability from the NIST CVE tracker [1]: 32 [1] https://nvd.nist.gov/vuln/detail/CVE-2013-4420
|