Home
last modified time | relevance | path

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

12345

/linux-6.14.4/arch/arm64/include/asm/
Drsi_cmds.h93 * @challenge: The challenge data to be used in the attestation token
95 * @size: Size of the challenge data in bytes.
108 rsi_attestation_token_init(const u8 *challenge, unsigned long size) in rsi_attestation_token_init() argument
112 /* The challenge must be at least 32bytes and at most 64bytes */ in rsi_attestation_token_init()
113 if (!challenge || size < 32 || size > 64) in rsi_attestation_token_init()
117 memcpy(&regs.a1, challenge, size); in rsi_attestation_token_init()
Drsi_smc.h101 * arg1 == Challenge value, bytes: 0 - 7
102 * arg2 == Challenge value, bytes: 8 - 15
103 * arg3 == Challenge value, bytes: 16 - 23
104 * arg4 == Challenge value, bytes: 24 - 31
105 * arg5 == Challenge value, bytes: 32 - 39
106 * arg6 == Challenge value, bytes: 40 - 47
107 * arg7 == Challenge value, bytes: 48 - 55
108 * arg8 == Challenge value, bytes: 56 - 63
/linux-6.14.4/drivers/virt/coco/arm-cca-guest/
Darm-cca-guest.c19 * @challenge: Pointer to the challenge data
20 * @challenge_size: Size of the challenge data
26 void *challenge; member
39 info->result = rsi_attestation_token_init(info->challenge, in arm_cca_attestation_init()
75 * Initialise the attestation token generation using the challenge data
80 * The challenge data must be at least 32 bytes and no more than 64 bytes. If
113 info.challenge = desc->inblob; in arm_cca_report_new()
/linux-6.14.4/drivers/target/iscsi/
Discsi_target_auth.c51 memset(chap->challenge, 0, MAX_CHAP_CHALLENGE_LEN); in chap_gen_challenge()
53 ret = get_random_bytes_wait(chap->challenge, chap->challenge_len); in chap_gen_challenge()
57 bin2hex(challenge_asciihex, chap->challenge, in chap_gen_challenge()
60 * Set CHAP_C, and copy the generated challenge into c_str. in chap_gen_challenge()
182 /* Tie the challenge length to the digest size */ in chap_server_open()
198 * Generate Challenge. in chap_server_open()
293 pr_err("Unable to allocate challenge buffer\n"); in chap_server_compute_hash()
390 ret = crypto_shash_finup(desc, chap->challenge, in chap_server_compute_hash()
393 pr_err("crypto_shash_finup() failed for challenge\n"); in chap_server_compute_hash()
460 pr_err("Unable to convert incoming challenge\n"); in chap_server_compute_hash()
[all …]
Discsi_target_auth.h37 unsigned char challenge[MAX_CHAP_CHALLENGE_LEN]; member
/linux-6.14.4/drivers/nvme/target/
Dauth.c281 u8 *challenge = req->sq->dhchap_c1; in nvmet_auth_host_hash() local
319 challenge = kmalloc(shash_len, GFP_KERNEL); in nvmet_auth_host_hash()
320 if (!challenge) { in nvmet_auth_host_hash()
328 challenge, shash_len); in nvmet_auth_host_hash()
347 ret = crypto_shash_update(shash, challenge, shash_len); in nvmet_auth_host_hash()
379 if (challenge != req->sq->dhchap_c1) in nvmet_auth_host_hash()
380 kfree(challenge); in nvmet_auth_host_hash()
395 u8 *challenge = req->sq->dhchap_c2; in nvmet_auth_ctrl_hash() local
433 challenge = kmalloc(shash_len, GFP_KERNEL); in nvmet_auth_ctrl_hash()
434 if (!challenge) { in nvmet_auth_ctrl_hash()
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.yaml4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml#
7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
14 This uses GPIO lines and a challenge & response mechanism to arbitrate who is
51 const: i2c-arb-gpio-challenge
106 compatible = "i2c-arb-gpio-challenge";
/linux-6.14.4/drivers/nvme/host/
Dauth.c320 dev_dbg(ctrl->device, "%s: qid %d ctrl challenge %*ph\n", in nvme_auth_set_dhchap_reply_data()
422 u8 buf[4], *challenge = chap->c1; in nvme_auth_dhchap_setup_host_response() local
450 challenge = kmalloc(chap->hash_len, GFP_KERNEL); in nvme_auth_dhchap_setup_host_response()
451 if (!challenge) { in nvme_auth_dhchap_setup_host_response()
458 chap->c1, challenge, in nvme_auth_dhchap_setup_host_response()
468 ret = crypto_shash_update(shash, challenge, chap->hash_len); in nvme_auth_dhchap_setup_host_response()
499 if (challenge != chap->c1) in nvme_auth_dhchap_setup_host_response()
500 kfree(challenge); in nvme_auth_dhchap_setup_host_response()
509 u8 buf[4], *challenge = chap->c2; in nvme_auth_dhchap_setup_ctrl_response() local
528 challenge = kmalloc(chap->hash_len, GFP_KERNEL); in nvme_auth_dhchap_setup_ctrl_response()
[all …]
/linux-6.14.4/tools/testing/selftests/net/netfilter/packetdrill/
Dconntrack_syn_challenge_ack.pkt2 // a challenge-ACK.
3 // Check that conntrack lets all packets pass, including the challenge ack,
24 // Challenge ACK, old incarnation.
Dconntrack_synack_reuse.pkt2 // Challenge ACK is supposed to pass through, RST reply should clear conntrack
25 // Won't expect this: challenge ack.
/linux-6.14.4/net/rxrpc/
Drxkad.c638 * issue a challenge
642 struct rxkad_challenge challenge; in rxkad_issue_challenge() local
654 challenge.version = htonl(2); in rxkad_issue_challenge()
655 challenge.nonce = htonl(conn->rxkad.nonce); in rxkad_issue_challenge()
656 challenge.min_level = htonl(0); in rxkad_issue_challenge()
657 challenge.__padding = 0; in rxkad_issue_challenge()
678 iov[1].iov_base = &challenge; in rxkad_issue_challenge()
679 iov[1].iov_len = sizeof(challenge); in rxkad_issue_challenge()
800 * respond to a challenge packet
806 struct rxkad_challenge challenge; in rxkad_respond_to_challenge() local
[all …]
Dprotocol.h42 #define RXRPC_PACKET_TYPE_CHALLENGE 6 /* connection security challenge (SRVR->CLNT) */
152 * Kerberos security type-2 challenge packet
155 __be32 version; /* version of this challenge type */
176 __be32 inc_nonce; /* challenge nonce + 1 */
/linux-6.14.4/drivers/i2c/muxes/
Di2c-arb-gpio-challenge.c3 * GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
186 { .compatible = "i2c-arb-gpio-challenge", },
195 .name = "i2c-arb-gpio-challenge",
205 MODULE_ALIAS("platform:i2c-arb-gpio-challenge");
DKconfig15 I2C multimaster arbitration scheme using GPIOs and a challenge &
20 will be called i2c-arb-gpio-challenge.
DMakefile5 obj-$(CONFIG_I2C_ARB_GPIO_CHALLENGE) += i2c-arb-gpio-challenge.o
/linux-6.14.4/drivers/staging/greybus/
Dauthentication.c144 u8 *challenge, u8 *result, u8 *auth_response, in cap_authenticate() argument
164 memcpy(request->challenge, challenge, sizeof(request->challenge)); in cap_authenticate()
249 authenticate->challenge, in cap_ioctl()
Dgreybus_authentication.h61 __u8 challenge[32]; member
/linux-6.14.4/drivers/thunderbolt/
Dtb_msgs.h255 u32 challenge[8]; member
264 u32 challenge[8]; member
418 u32 challenge[8]; member
448 u32 challenge[8]; member
Ddomain.c694 * tb_domain_challenge_switch_key() - Challenge and approve switch
699 * random challenge and sends it to the switch. The switch responds to
700 * this and if the response matches our random challenge, the switch is
707 u8 challenge[TB_SWITCH_KEY_SIZE]; in tb_domain_challenge_switch_key() local
723 get_random_bytes(challenge, sizeof(challenge)); in tb_domain_challenge_switch_key()
724 ret = tb->cm_ops->challenge_switch_key(tb, sw, challenge, response); in tb_domain_challenge_switch_key()
746 ret = crypto_shash_digest(shash, challenge, sizeof(hmac), hmac); in tb_domain_challenge_switch_key()
/linux-6.14.4/net/ceph/
Dauth_x.c685 dout("handle_reply got server challenge %llx\n", in ceph_x_handle_reply()
793 void *challenge, int challenge_len, in decrypt_authorizer_challenge() argument
800 ret = __ceph_x_decrypt(secret, challenge, challenge_len); in decrypt_authorizer_challenge()
805 dp = challenge + sizeof(struct ceph_x_encrypt_header); in decrypt_authorizer_challenge()
819 void *challenge, int challenge_len) in ceph_x_add_authorizer_challenge() argument
825 ret = decrypt_authorizer_challenge(&au->session_key, challenge, in ceph_x_add_authorizer_challenge()
828 pr_err("failed to decrypt authorize challenge: %d", ret); in ceph_x_add_authorizer_challenge()
834 pr_err("failed to encrypt authorizer w/ challenge: %d", ret); in ceph_x_add_authorizer_challenge()
/linux-6.14.4/Documentation/admin-guide/
Dthunderbolt.rst69 a challenge that should match the expected one based on a random key
148 Next time the device is plugged in the user can verify (challenge) the
154 If the challenge the device returns back matches the one we expect based
156 However, if the challenge fails no tunnels are created and error is
/linux-6.14.4/fs/smb/client/
Dcifsencrypt.c387 /* Server has provided av pairs/target info in the type 2 challenge
502 offsetof(struct ntlmv2_resp, challenge.key[0])); in CalcNTLMv2_response()
517 memcpy(ntlmv2->challenge.key, ses->ntlmssp->cryptkey, CIFS_SERVER_CHALLENGE_SIZE); in CalcNTLMv2_response()
519 memcpy(ntlmv2->challenge.key, ses->server->cryptkey, CIFS_SERVER_CHALLENGE_SIZE); in CalcNTLMv2_response()
521 rc = crypto_shash_update(hmacmd5, ntlmv2->challenge.key, hash_len); in CalcNTLMv2_response()
/linux-6.14.4/include/uapi/linux/netfilter/
Dnf_conntrack_tcp.h46 /* Marks possibility for expected RFC5961 challenge ACK */
/linux-6.14.4/drivers/gpu/drm/ttm/tests/
DTODO24 a challenge, but is worth trying. Look at selftests like
/linux-6.14.4/include/linux/
Dnvme-auth.h36 u8 *challenge, u8 *aug, size_t hlen);

12345