Home
last modified time | relevance | path

Searched full:challenge (Results 1 – 25 of 102) sorted by relevance

12345

/openbmc/ipmitool/src/plugins/lan/
H A Dauth.c171 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 Dlan.c1690 * 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/linux/drivers/target/iscsi/
Discsi_target_auth.c
Discsi_target_auth.h
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/
H A DResource.interface.yaml24 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/linux/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.yaml
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/Entry/
H A DSystem.interface.yaml41 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/u-boot/arch/arm/mach-imx/mx7/
H A Dsoc.c318 * 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/phosphor-net-ipmid/command/
H A Drakp12.hpp56 * 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/linux/net/rxrpc/
Dprotocol.h
/openbmc/linux/drivers/staging/rts5208/
Drtsx_scsi.h
/openbmc/u-boot/drivers/i2c/muxes/
H A DMakefile4 obj-$(CONFIG_I2C_ARB_GPIO_CHALLENGE) += i2c-arb-gpio-challenge.o
H A DKconfig24 I2C multimaster arbitration scheme using GPIOs and a challenge &
/openbmc/linux/net/ceph/
Dauth_x.c
/openbmc/linux/include/uapi/linux/netfilter/
Dnf_conntrack_tcp.h
/openbmc/linux/Documentation/admin-guide/
Dthunderbolt.rst
/openbmc/openbmc/poky/meta/recipes-core/dropbear/dropbear/
H A D0005-dropbear-enable-pam.patch32 * PAM challenge/response.
/openbmc/linux/drivers/media/usb/hdpvr/
Dhdpvr-core.c
/openbmc/linux/drivers/staging/greybus/Documentation/firmware/
Dauthenticate.c
Dfirmware-management
/openbmc/u-boot/doc/
H A DREADME.i2c23 i2c-arb-gpio-challenge for the implementation.
/openbmc/linux/Documentation/ABI/testing/
Dsysfs-bus-thunderbolt
/openbmc/linux/drivers/comedi/drivers/ni_routing/
DREADME
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/
H A Daz.py59 fetchcmd += " --user=%s --password=%s --auth-no-challenge" % (ud.user, ud.pswd)
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DCertificate.v1_10_0.json511 … "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…

12345