| /openbmc/ipmitool/src/plugins/lan/ |
| H A D | auth.c | 171 uint8_t challenge[16]; in ipmi_auth_special() local 174 memset(challenge, 0, 16); in ipmi_auth_special() 183 challenge[i] = s->challenge[i] ^ md[i]; in ipmi_auth_special() 189 MD5_Update(&ctx, (const uint8_t *)challenge, 16); in ipmi_auth_special() 197 uint8_t challenge[16]; in ipmi_auth_special() 199 memset(challenge, 0, 16); in ipmi_auth_special() 208 challenge[i] = s->challenge[i] ^ digest[i]; in ipmi_auth_special() 214 md5_append(&state, (const md5_byte_t *)challenge, 16); in ipmi_auth_special()
|
| H A D | lan.c | 1690 * IPMI Get Session Challenge Command 1691 * returns a temporary session ID and 16 byte challenge string 1713 lprintf(LOG_ERR, "Get Session Challenge command failed"); in ipmi_get_session_challenge_cmd() 1728 lprintf(LOG_ERR, "Get Session Challenge command failed: %s", in ipmi_get_session_challenge_cmd() 1735 memcpy(s->challenge, rsp->data + 4, 16); in ipmi_get_session_challenge_cmd() 1739 lprintf(LOG_DEBUG, " Challenge : %s", buf2str(s->challenge, 16)); in ipmi_get_session_challenge_cmd() 1770 memcpy(msg_data + 2, s->challenge, 16); in ipmi_activate_session_cmd() 1952 * about supported challenge/response authentication types 1953 * 3. send "Get Session Challenge" command with AUTHTYPE = none 1955 * packet will contain challenge string and temporary session ID.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Resource.interface.yaml | 24 On some host implementations a user-challenge need to be provided by 31 Model (PLDM), is used. The host validates the provided user-challenge 32 against this ACL. If the user-challenge doesn't match any entry in the 70 User challenge provided is not valid
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/Entry/ |
| H A D | System.interface.yaml | 41 On some host implementations a user-challenge need to be provided by 48 Model (PLDM), is used. The host validates the provided user-challenge 49 against this ACL. If the user-challenge doesn't match any entry in the 92 The user challenge provided is not valid
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | CertificateEnrollment.v1_0_0.json | 13 "Dns01": "DNS challenge type for domain validation.", 14 "Http01": "HTTP challenge type for domain validation." 17 …"Dns01": "This value shall indicate the RFC8555-defined dns-01 challenge type for domain validatio… 18 …"Http01": "This value shall indicate the RFC8555-defined http-01 challenge type for domain validat… 50 "description": "The ACME challenge type used for domain validation.", 51 …"longDescription": "This property shall contain the ACME challenge type used for domain validation… 145 … "description": "The challenge password to apply to the certificate for revocation requests.", 146 …"longDescription": "This property shall contain the challenge password to apply to the certificate… 661 "description": "The challenge password for SCEP enrollment.", 662 …"longDescription": "This property shall contain the challenge password used for SCEP enrollment. …
|
| H A D | Certificate.v1_11_0.json | 511 … "description": "The challenge password to apply to the certificate for revocation requests.", 512 …"longDescription": "This property shall contain the challenge password to apply to the certificate… 608 … "description": "The challenge password to apply to the certificate for revocation requests.", 609 …"longDescription": "This property shall contain the challenge password to apply to the certificate…
|
| H A D | Key.v1_4_1.json | 277 …"DHHC": "Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authentication Prot… 282 …ue shall indicate the Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authen…
|
| H A D | KeyPolicy.v1_0_1.json | 330 …"DHHC": "Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authentication Prot… 335 …ue shall indicate the Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authen…
|
| /openbmc/phosphor-net-ipmid/command/ |
| H A D | rakp12.hpp | 56 * mutual challenges for a challenge/response. (Unlike IPMI v1.5, the v2.0/RMCP+ 57 * challenge/response is symmetric. I.e. the remote console and BMC both issues
|
| /openbmc/u-boot/arch/arm/mach-imx/mx7/ |
| H A D | soc.c | 318 * FSL-wide unique, encoded LOT ID STD II/SJC CHALLENGE/ Unique ID 322 * The X-coordinate of the die location on the wafer/SJC CHALLENGE/ Unique ID 324 * The Y-coordinate of the die location on the wafer/SJC CHALLENGE/ Unique ID 327 * CHALLENGE/ Unique ID 329 * FSL-wide unique, encoded LOT ID STD II/SJC CHALLENGE/ Unique ID
|
| /openbmc/u-boot/drivers/i2c/muxes/ |
| H A D | Makefile | 4 obj-$(CONFIG_I2C_ARB_GPIO_CHALLENGE) += i2c-arb-gpio-challenge.o
|
| H A D | Kconfig | 24 I2C multimaster arbitration scheme using GPIOs and a challenge &
|
| H A D | i2c-arb-gpio-challenge.c | 134 { .compatible = "i2c-arb-gpio-challenge" },
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | CertificateEnrollment_v1.xml | 169 <Annotation Term="OData.Description" String="HTTP challenge type for domain validation."/> 170 …cription" String="This value shall indicate the RFC8555-defined http-01 challenge type for domain … 173 <Annotation Term="OData.Description" String="DNS challenge type for domain validation."/> 174 …scription" String="This value shall indicate the RFC8555-defined dns-01 challenge type for domain … 199 …<Annotation Term="OData.Description" String="The ACME challenge type used for domain validation."/> 200 …rm="OData.LongDescription" String="This property shall contain the ACME challenge type used for do… 210 … <Annotation Term="OData.Description" String="The challenge password for SCEP enrollment."/> 211 …on Term="OData.LongDescription" String="This property shall contain the challenge password used fo… 316 …<Annotation Term="OData.Description" String="The challenge password to apply to the certificate fo… 317 …on Term="OData.LongDescription" String="This property shall contain the challenge password to appl…
|
| H A D | KeyPolicy_v1.xml | 133 ….Description" String="Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authen… 134 …ue shall indicate the Diffie-Hellman Hashed Message Authentication Code Challenge Handshake Authen…
|
| /openbmc/openbmc/poky/meta/recipes-core/dropbear/dropbear/ |
| H A D | 0005-dropbear-enable-pam.patch | 32 * PAM challenge/response.
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 23 i2c-arb-gpio-challenge for the implementation.
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | az.py | 59 fetchcmd += " --user=%s --password=%s --auth-no-challenge" % (ud.user, ud.pswd)
|
| /openbmc/phosphor-debug-collector/dump-extensions/openpower-dumps/ |
| H A D | resource_dump_entry.hpp | 54 * @param[in] usrChallenge - User Challenge needed by host to validate the
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Certificate.v1_11_0.json | 511 … "description": "The challenge password to apply to the certificate for revocation requests.", 512 …"longDescription": "This property shall contain the challenge password to apply to the certificate… 608 … "description": "The challenge password to apply to the certificate for revocation requests.", 609 …"longDescription": "This property shall contain the challenge password to apply to the certificate…
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | x86-fit-boot.txt | 22 mode was something of a challenge, so putting this logic in the kernel seemed 53 quite a challenge to extract anything from it. This bzImage format has become
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/CSR/ |
| H A D | Create.interface.yaml | 30 The challenge password to be applied to the certificate for
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/vpnc/vpnc/ |
| H A D | long-help | 37 enable interactive extended authentication (for challenge response auth)
|
| /openbmc/ipmitool/include/ipmitool/ |
| H A D | ipmi_intf.h | 94 uint8_t challenge[16]; member
|
| /openbmc/docs/designs/ |
| H A D | gpio-based-cable-presence.md | 128 of discrete sensors. The challenge here is that type12 record also has a limit
|