| /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 | 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()
|
| /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 &
|
| /openbmc/openbmc/poky/meta/recipes-core/dropbear/dropbear/ |
| H A D | 0005-dropbear-enable-pam.patch | 32 * PAM challenge/response.
|
| /openbmc/u-boot/arch/arm/include/asm/arch-tegra/ |
| H A D | bpmp_abi.h | 208 uint32_t challenge; member
431 uint32_t challenge; member
|
| /openbmc/ipmitool/include/ipmitool/ |
| H A D | ipmi_intf.h | 94 uint8_t challenge[16]; member
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 23 i2c-arb-gpio-challenge for the implementation.
|
| /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/openbmc/meta-openembedded/meta-networking/recipes-connectivity/vpnc/vpnc/ |
| H A D | long-help | 37 enable interactive extended authentication (for challenge response auth)
|
| /openbmc/qemu/ui/ |
| H A D | vnc.h | 296 char challenge[VNC_AUTH_CHALLENGE_SIZE]; member
|
| H A D | vnc.c | 2828 memcpy(response, vs->challenge, VNC_AUTH_CHALLENGE_SIZE); in protocol_client_auth_vnc()
2830 /* Calculate the expected challenge response */ in protocol_client_auth_vnc()
2849 vs->challenge, in protocol_client_auth_vnc()
2853 trace_vnc_auth_fail(vs, vs->auth, "cannot encrypt challenge response", in protocol_client_auth_vnc()
2859 /* Compare expected vs actual challenge response */ in protocol_client_auth_vnc()
2861 trace_vnc_auth_fail(vs, vs->auth, "mis-matched challenge response", ""); in protocol_client_auth_vnc()
2884 if (qcrypto_random_bytes(vs->challenge, sizeof(vs->challenge), &err)) { in start_auth_vnc()
2892 /* Send client a 'random' challenge */ in start_auth_vnc()
2893 vnc_write(vs, vs->challenge, sizeo in start_auth_vnc()
[all...] |
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/pidgin/pidgin-sipe/ |
| H A D | 0001-Migrate-to-use-g_memdup2.patch | 82 /* server challenge (nonce) */
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | exynos5250-snow.dts | 98 compatible = "i2c-arb-gpio-challenge";
|
| /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
|
| H A D | external-sensor.md | 194 A challenge of generalizing the timeout feature into _ExternalSensor_, however,
|
| H A D | pldm-stack.md | 348 plus sending messages concurrently would be a challenge.
|
| /openbmc/qemu/docs/devel/ |
| H A D | tcg.rst | 130 Self-modifying code is a special challenge in x86 emulation because no
|
| /openbmc/u-boot/scripts/ |
| H A D | spelling.txt | 228 challange||challenge
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/pam-ssh-agent-auth/ |
| H A D | 0001-Adapt-to-OpenSSL-1.1.1.patch | 63 pamsshagentauth_buffer_put_bignum(&buffer, challenge);
|
| /openbmc/u-boot/tools/binman/ |
| H A D | README | 754 The design challenge is to make it easy to create simple images, while
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | packages.rst | 101 Given a primary challenge of any build system and its users is how to
|