nvme: In-band authentication support
Subsystems (5)
Hannes Reinecke
maintainerv8 cover nvme: In-band authentication support
Hi all,
recent updates to the NVMe spec have added definitions for in-band authentication, and seeing that it provides some real benefit especially for NVMe-TCP here's an attempt to implement it.
The ffdhe implementation given here is preliminary; there is a patchset from Nicolai Stange to implement FFDHE as a 'real' crypto algorithm, and also implements ephemeral keys for in-kernel DH. Once that is merged I'll be updating this patchset.
Also note that this is just for in-band authentication. Secure concatenation (ie starting TLS with the negotiated parameters) is not implemented; one would need to update the kernel TLS implementation for this, which at this time is beyond scope.
The nvme-cli support has already been merged; please use the latest nvme-cli git repository to build the most recent version.
A copy of this patchset can be found atgit://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel
branch auth.v8
As usual, comments and reviews are welcome.
Changes to v7:
- Space out hash list and dhgroup list in nvme negotiate data to be conformant with the spec
- Update sequence number handling to start with a random value and ignore '0' as mandated by the spec
- Update nvme_auth_generate_key to return the key as suggested by Sagi
- Add nvmet_parse_fabrics_io_cmd() as suggested by hch
Changes to v6:
- Use 'u8' for DH group id and hash id
- Use 'struct nvme_dhchap_key'
- Rename variables to drop 'DHCHAP'
- Include reviews from Chaitanya
Changes to v5:
- Unify nvme_auth_generate_key()
- Unify nvme_auth_extract_key()
- Fixed bug where re-authentication with wrong controller key would not fail
- Include reviews from Sagi
Changes to v4:
- Validate against blktest suite
- Fixup base64 decoding
- Transform secret with correct hmac algorithm
Changes to v3:
- Renamed parameter to 'dhchap_ctrl_key'
- Fixed bi-directional authentication
- Included reviews from Sagi
- Fixed base64 algorithm for transport encoding
Changes to v2:
- Dropped non-standard algorithms
- Reworked base64 based on fs/crypto/fname.c
- Fixup crash with no keys
Changes to the original submission:
- Included reviews from Vladislav
- Included reviews from Sagi
- Implemented re-authentication support
- Fixed up key handling
Hannes Reinecke (12):
crypto: add crypto_has_shash()
crypto: add crypto_has_kpp()
crypto/ffdhe: Finite Field DH Ephemeral Parameters lib/base64: RFC4648-compliant base64 encoding
nvme: add definitions for NVMe In-Band authentication
nvme-fabrics: decode 'authentication required' connect error
nvme: Implement In-Band authentication
nvme-auth: Diffie-Hellman key exchange support
nvmet: parse fabrics commands on io queues
nvmet: Implement basic In-Band Authentication
nvmet-auth: Diffie-Hellman key exchange support
nvmet-auth: expire authentication sessions
crypto/Kconfig | 8 + crypto/Makefile | 1 + crypto/ffdhe_helper.c | 880 +++++++++++++ crypto/kpp.c | 6 + crypto/shash.c | 6 + drivers/nvme/host/Kconfig | 12 + drivers/nvme/host/Makefile | 1 + drivers/nvme/host/auth.c | 1569 ++++++++++++++++++++++++ drivers/nvme/host/auth.h | 42 + drivers/nvme/host/core.c | 141 ++- drivers/nvme/host/fabrics.c | 83 +- drivers/nvme/host/fabrics.h | 7 + drivers/nvme/host/nvme.h | 31 + drivers/nvme/host/rdma.c | 1 + drivers/nvme/host/tcp.c | 1 + drivers/nvme/host/trace.c | 32 + drivers/nvme/target/Kconfig | 13 + drivers/nvme/target/Makefile | 1 + drivers/nvme/target/admin-cmd.c | 6 +- drivers/nvme/target/auth.c | 523 ++++++++ drivers/nvme/target/configfs.c | 138 ++- drivers/nvme/target/core.c | 15 + drivers/nvme/target/fabrics-cmd-auth.c | 534 ++++++++ drivers/nvme/target/fabrics-cmd.c | 55 +- drivers/nvme/target/nvmet.h | 75 +- include/crypto/ffdhe.h | 24 + include/crypto/hash.h | 2 + include/crypto/kpp.h | 2 + include/linux/base64.h | 16 + include/linux/nvme.h | 188 ++- lib/Makefile | 2 +- lib/base64.c | 103 ++ 32 files changed, 4503 insertions(+), 15 deletions(-) create mode 100644 crypto/ffdhe_helper.c create mode 100644 drivers/nvme/host/auth.c create mode 100644 drivers/nvme/host/auth.h create mode 100644 drivers/nvme/target/auth.c create mode 100644 drivers/nvme/target/fabrics-cmd-auth.c create mode 100644 include/crypto/ffdhe.h create mode 100644 include/linux/base64.h create mode 100644 lib/base64.c
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 1/12 crypto: add crypto_has_shash()
Add helper function to determine if a given synchronous hash is supported.
--- crypto/shash.c | 6 ++++++ include/crypto/hash.h | 2 ++ 2 files changed, 8 insertions(+)
crypto/shash.c +6 -0
@@ -521,6 +521,12 @@ struct crypto_shash *crypto_alloc_shash(const char *alg_name, u32 type, }EXPORT_SYMBOL_GPL (crypto_alloc_shash); +int crypto_has_shash (const char *alg_name,u32 type,u32 mask) +{ +return crypto_type_has_alg (alg_name, &crypto_shash_type, type, mask); +} +EXPORT_SYMBOL_GPL (crypto_has_shash); +static int shash_prepare_alg (struct shash_alg *alg) {struct crypto_alg *base = &alg->base;
include/crypto/hash.h +2 -0
@@ -718,6 +718,8 @@ static inline void ahash_request_set_crypt(struct ahash_request *req,struct crypto_shash *crypto_alloc_shash (const char *alg_name,u32 type,u32 mask); +int crypto_has_shash (const char *alg_name,u32 type,u32 mask); +static inline struct crypto_tfm *crypto_shash_tfm (struct crypto_shash *tfm) {return &tfm->base;
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 2/12 crypto: add crypto_has_kpp()
In reply to Hannes ReineckeAdd helper function to determine if a given key-agreement protocol primitive is supported.
--- crypto/kpp.c | 6 ++++++ include/crypto/kpp.h | 2 ++ 2 files changed, 8 insertions(+)
crypto/kpp.c +6 -0
@@ -87,6 +87,12 @@ struct crypto_kpp *crypto_alloc_kpp(const char *alg_name, u32 type, u32 mask) }EXPORT_SYMBOL_GPL (crypto_alloc_kpp); +int crypto_has_kpp (const char *alg_name,u32 type,u32 mask) +{ +return crypto_type_has_alg (alg_name, &crypto_kpp_type, type, mask); +} +EXPORT_SYMBOL_GPL (crypto_has_kpp); +static void kpp_prepare_alg (struct kpp_alg *alg) {struct crypto_alg *base = &alg->base;
include/crypto/kpp.h +2 -0
@@ -104,6 +104,8 @@ struct kpp_alg {*/ struct crypto_kpp *crypto_alloc_kpp (const char *alg_name,u32 type,u32 mask); +int crypto_has_kpp (const char *alg_name,u32 type,u32 mask); +static inline struct crypto_tfm *crypto_kpp_tfm (struct crypto_kpp *tfm) {return &tfm->base;
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 3/12 crypto/ffdhe: Finite Field DH Ephemeral Parameters
In reply to Hannes ReineckeAdd helper functions to generaten Finite Field DH Ephemeral Parameters as specified in RFC 7919.
--- crypto/Kconfig | 8 + crypto/Makefile | 1 + crypto/ffdhe_helper.c | 880 +++++++++++++++++++++++++++++++++++++++++ include/crypto/ffdhe.h | 24 ++ 4 files changed, 913 insertions(+) create mode 100644 crypto/ffdhe_helper.c create mode 100644 include/crypto/ffdhe.h
crypto/Kconfig +8 -0
@@ -231,6 +231,14 @@ config CRYPTO_DH help Generic implementation of the Diffie-Hellman algorithm. +config CRYPTO_FFDHE + tristate "Finite Field DH (RFC 7919) ephemeral parameters" + select CRYPTO_DH + select CRYPTO_KPP + select CRYPTO_RNG_DEFAULT + help + Generic implementation of the Finite Field DH algorithm + config CRYPTO_ECC tristate select CRYPTO_RNG_DEFAULT
crypto/Makefile +1 -0
@@ -178,6 +178,7 @@ obj-$(CONFIG_CRYPTO_OFB) += ofb.o obj-$(CONFIG_CRYPTO_ECC) += ecc.o obj-$(CONFIG_CRYPTO_ESSIV) += essiv.o obj-$(CONFIG_CRYPTO_CURVE25519) += curve25519-generic.o +obj-$(CONFIG_CRYPTO_FFDHE) += ffdhe_helper.o ecdh_generic-y += ecdh.o ecdh_generic-y += ecdh_helper.o
crypto/ffdhe_helper.c new file +880 -0
880 lines not on this page · raw message
include/crypto/ffdhe.h new file +24 -0
@@ -0,0 +1,24 @@ +/* SPDX-License-Identifier: GPL-2.0-or-later */ +/* +* Finite-Field Diffie-Hellman definition according to RFC 7919 +* +* Copyright (c) 2021, SUSE Software Products +* Authors: Hannes Reinecke <[email protected]> +*/ +#ifndef _CRYPTO_FFDHE_ +#define _CRYPTO_FFDHE_ + +/** +* crypto_ffdhe_params() - Generate FFDHE params +* @params: DH params +* @bits: Bitsize of the FFDHE parameters +* +* This functions sets the FFDHE parameter for @bits in @params. +* Valid bit sizes are 2048, 3072, 4096, 6144, or 8194. +* +* Returns: 0 on success, errno on failure. +*/ + +int crypto_ffdhe_params (struct dh *p,int bits); + +#endif /* _CRYPTO_FFDHE_H */
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 4/12 lib/base64: RFC4648-compliant base64 encoding
In reply to Hannes ReineckeAdd RFC4648-compliant base64 encoding and decoding routines, based on the base64url encoding in fs/crypto/fname.c.
--- include/linux/base64.h | 16 +++++++ lib/Makefile | 2 +- lib/base64.c | 103 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 120 insertions(+), 1 deletion(-) create mode 100644 include/linux/base64.h create mode 100644 lib/base64.c
include/linux/base64.h new file +16 -0
@@ -0,0 +1,16 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* base64 encoding, lifted from fs/crypto/fname.c. +*/ + +#ifndef _LINUX_BASE64_H +#define _LINUX_BASE64_H + +#include <linux/types.h> + +#define BASE64_CHARS (nbytes) DIV_ROUND_UP((nbytes) * 4, 3) + +int base64_encode (const u8 *src,int len,char *dst); +int base64_decode (const char *src,int len,u8 *dst); + +#endif /* _LINUX_BASE64_H */
lib/Makefile +1 -1
@@ -46,7 +46,7 @@ obj-y += bcd.o sort.o parser.o debug_locks.o random32.o \ bust_spinlocks.o kasprintf.o bitmap.o scatterlist.o \ list_sort.o uuid.o iov_iter.o clz_ctz.o \ bsearch.o find_bit.o llist.o memweight.o kfifo.o \ - percpu-refcount.o rhashtable.o \ + percpu-refcount.o rhashtable.o base64.o \ once.o refcount.o usercopy.o errseq.o bucket_locks.o \ generic-radix-tree.o obj-$(CONFIG_STRING_SELFTEST) += test_string.o
lib/base64.c new file +103 -0
103 lines not on this page · raw message
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 5/12 nvme: add definitions for NVMe In-Band authentication
In reply to Hannes ReineckeAdd new definitions for NVMe In-band authentication as defined in the NVMe Base Specification v2.0.
--- include/linux/nvme.h | 188 ++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 187 insertions(+), 1 deletion(-)
include/linux/nvme.h +187 -1
@@ -19,6 +19,7 @@#define NVMF_TRSVCID_SIZE 32#define NVMF_TRADDR_SIZE 256#define NVMF_TSAS_SIZE 256 +#define NVMF_AUTH_HASH_LEN 64#define NVME_DISC_SUBSYS_NAME "nqn.2014-08.org.nvmexpress.discovery"
@@ -1278,6 +1279,8 @@ enum nvmf_capsule_command { nvme_fabrics_type_property_set =0x00 , nvme_fabrics_type_connect =0x01 , nvme_fabrics_type_property_get =0x04 , + nvme_fabrics_type_auth_send =0x05 , + nvme_fabrics_type_auth_receive = 0x06, };#define nvme_fabrics_type_name (type) { type, #type }
@@ -1285,7 +1288,9 @@ enum nvmf_capsule_command {__print_symbolic (type, \nvme_fabrics_type_name (nvme_fabrics_type_property_set), \nvme_fabrics_type_name (nvme_fabrics_type_connect), \ -nvme_fabrics_type_name (nvme_fabrics_type_property_get)) +nvme_fabrics_type_name (nvme_fabrics_type_property_get), \ +nvme_fabrics_type_name (nvme_fabrics_type_auth_send), \ +nvme_fabrics_type_name (nvme_fabrics_type_auth_receive))/* * If not fabrics command, fctype will be ignored.
@@ -1415,6 +1420,185 @@ struct nvmf_property_get_command {__u8 resv4[16 ]; }; +struct nvmf_auth_send_command { +__u8 opcode; +__u8 resv1; +__u16 command_id; +__u8 fctype; +__u8 resv2[19 ]; +union nvme_data_ptr dptr; +__u8 resv3; +__u8 spsp0; +__u8 spsp1; +__u8 secp; +__le32 tl; +__u8 resv4[16 ]; +}; + +struct nvmf_auth_receive_command { +__u8 opcode; +__u8 resv1; +__u16 command_id; +__u8 fctype; +__u8 resv2[19 ]; +union nvme_data_ptr dptr; +__u8 resv3; +__u8 spsp0; +__u8 spsp1; +__u8 secp; +__le32 al; +__u8 resv4[16 ]; +}; + +/* Value for secp */ +enum { +NVME_AUTH_DHCHAP_PROTOCOL_IDENTIFIER =0xe9 , +}; + +/* Defined value for auth_type */ +enum { +NVME_AUTH_COMMON_MESSAGES =0x00 , +NVME_AUTH_DHCHAP_MESSAGES =0x01 , +}; + +/* Defined messages for auth_id */ +enum { +NVME_AUTH_DHCHAP_MESSAGE_NEGOTIATE =0x00 , +NVME_AUTH_DHCHAP_MESSAGE_CHALLENGE =0x01 , +NVME_AUTH_DHCHAP_MESSAGE_REPLY =0x02 , +NVME_AUTH_DHCHAP_MESSAGE_SUCCESS1 =0x03 , +NVME_AUTH_DHCHAP_MESSAGE_SUCCESS2 =0x04 , +NVME_AUTH_DHCHAP_MESSAGE_FAILURE2 =0xf0 , +NVME_AUTH_DHCHAP_MESSAGE_FAILURE1 =0xf1 , +}; + +struct nvmf_auth_dhchap_protocol_descriptor { +__u8 authid; +__u8 rsvd; +__u8 halen; +__u8 dhlen; +__u8 idlist[60 ]; +}; + +enum { +NVME_AUTH_DHCHAP_AUTH_ID =0x01 , +}; + +/* Defined hash functions for DH-HMAC-CHAP authentication */ +enum { +NVME_AUTH_HASH_SHA256 =0x01 , +NVME_AUTH_HASH_SHA384 =0x02 , +NVME_AUTH_HASH_SHA512 =0x03 , +NVME_AUTH_HASH_INVALID =0xff , +}; + +/* Defined Diffie-Hellman group identifiers for DH-HMAC-CHAP authentication */ +enum { +NVME_AUTH_DHGROUP_NULL =0x00 , +NVME_AUTH_DHGROUP_2048 =0x01 , +NVME_AUTH_DHGROUP_3072 =0x02 , +NVME_AUTH_DHGROUP_4096 =0x03 , +NVME_AUTH_DHGROUP_6144 =0x04 , +NVME_AUTH_DHGROUP_8192 =0x05 , +NVME_AUTH_DHGROUP_INVALID =0xff , +}; + +union nvmf_auth_protocol { +struct nvmf_auth_dhchap_protocol_descriptor dhchap; +}; + +struct nvmf_auth_dhchap_negotiate_data { +__u8 auth_type; +__u8 auth_id; +__le16 rsvd; +__le16 t_id; +__u8 sc_c; +__u8 napd; +union nvmf_auth_protocol auth_protocol[]; +}; + +struct nvmf_auth_dhchap_challenge_data { +__u8 auth_type; +__u8 auth_id; +__u16 rsvd1; +__le16 t_id; +__u8 hl; +__u8 rsvd2; +__u8 hashid; +__u8 dhgid; +__le16 dhvlen; +__le32 seqnum; +/* 'hl' bytes of challenge value */ +__u8 cval[]; +/* followed by 'dhvlen' bytes of DH value */ +}; + +struct nvmf_auth_dhchap_reply_data { +__u8 auth_type; +__u8 auth_id; +__le16 rsvd1; +__le16 t_id; +__u8 hl; +__u8 rsvd2; +__u8 cvalid; +__u8 rsvd3; +__le16 dhvlen; +__le32 seqnum; +/* 'hl' bytes of response data */ +__u8 rval[]; +/* followed by 'hl' bytes of Challenge value */ +/* followed by 'dhvlen' bytes of DH value */ +}; + +enum { +NVME_AUTH_DHCHAP_RESPONSE_VALID = (1 <<0 ), +}; + +struct nvmf_auth_dhchap_success1_data { +__u8 auth_type; +__u8 auth_id; +__le16 rsvd1; +__le16 t_id; +__u8 hl; +__u8 rsvd2; +__u8 rvalid; +__u8 rsvd3[7 ]; +/* 'hl' bytes of response value if 'rvalid' is set */ +__u8 rval[]; +}; + +struct nvmf_auth_dhchap_success2_data { +__u8 auth_type; +__u8 auth_id; +__le16 rsvd1; +__le16 t_id; +__u8 rsvd2[10 ]; +}; + +struct nvmf_auth_dhchap_failure_data { +__u8 auth_type; +__u8 auth_id; +__le16 rsvd1; +__le16 t_id; +__u8 rescode; +__u8 rescode_exp; +}; + +enum { +NVME_AUTH_DHCHAP_FAILURE_REASON_FAILED =0x01 , +}; + +enum { +NVME_AUTH_DHCHAP_FAILURE_FAILED =0x01 , +NVME_AUTH_DHCHAP_FAILURE_NOT_USABLE =0x02 , +NVME_AUTH_DHCHAP_FAILURE_CONCAT_MISMATCH =0x03 , +NVME_AUTH_DHCHAP_FAILURE_HASH_UNUSABLE =0x04 , +NVME_AUTH_DHCHAP_FAILURE_DHGROUP_UNUSABLE =0x05 , +NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD =0x06 , +NVME_AUTH_DHCHAP_FAILURE_INCORRECT_MESSAGE =0x07 , +}; + +struct nvme_dbbuf {__u8 opcode;__u8 flags;
@@ -1458,6 +1642,8 @@ struct nvme_command {struct nvmf_connect_command connect;struct nvmf_property_set_command prop_set;struct nvmf_property_get_command prop_get; +struct nvmf_auth_send_command auth_send; +struct nvmf_auth_receive_command auth_receive;struct nvme_dbbuf dbbuf;struct nvme_directive_cmd directive; };
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 6/12 nvme-fabrics: decode 'authentication required' connect error
In reply to Hannes ReineckeThe 'connect' command might fail with NVME_SC_AUTH_REQUIRED, so we should be decoding this error, too.
--- drivers/nvme/host/fabrics.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/nvme/host/fabrics.c +4 -0
@@ -332,6 +332,10 @@ static void nvmf_log_connect_error(struct nvme_ctrl *ctrl,dev_err (ctrl->device,"Connect command failed: host path error\n" );break ; +case NVME_SC_AUTH_REQUIRED : +dev_err (ctrl->device, +"Connect command failed: authentication required\n" ); +break ;default : dev_err(ctrl->device, "Connect command failed, error wo/DNR bit: %d\n",
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 7/12 nvme: Implement In-Band authentication
In reply to Hannes ReineckeImplement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds two new fabric options 'dhchap_secret' to specify the pre-shared key (in ASCII respresentation according to NVMe 2.0 section 8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specify the pre-shared controller key for bi-directional authentication of both the host and the controller.
Re-authentication can be triggered by writing the PSK into the new controller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.
--- drivers/nvme/host/Kconfig | 11 + drivers/nvme/host/Makefile | 1 + drivers/nvme/host/auth.c | 1169 +++++++++++++++++++++++++++++++++++ drivers/nvme/host/auth.h | 34 + drivers/nvme/host/core.c | 141 ++++- drivers/nvme/host/fabrics.c | 79 ++- drivers/nvme/host/fabrics.h | 7 + drivers/nvme/host/nvme.h | 31 + drivers/nvme/host/rdma.c | 1 + drivers/nvme/host/tcp.c | 1 + drivers/nvme/host/trace.c | 32 + 11 files changed, 1500 insertions(+), 7 deletions(-) create mode 100644 drivers/nvme/host/auth.c create mode 100644 drivers/nvme/host/auth.h
drivers/nvme/host/Kconfig +11 -0
@@ -83,3 +83,14 @@ config NVME_TCP from https://github.com/linux-nvme/nvme-cli. If unsure, say N. + +config NVME_AUTH + bool "NVM Express over Fabrics In-Band Authentication" + depends on NVME_CORE + select CRYPTO_HMAC + select CRYPTO_SHA256 + select CRYPTO_SHA512 + help + This provides support for NVMe over Fabrics In-Band Authentication. + + If unsure, say N.
drivers/nvme/host/Makefile +1 -0
@@ -15,6 +15,7 @@ nvme-core-$(CONFIG_NVME_MULTIPATH) += multipath.o nvme-core-$(CONFIG_BLK_DEV_ZONED) += zns.o nvme-core-$(CONFIG_FAULT_INJECTION_DEBUG_FS) += fault_inject.o nvme-core-$(CONFIG_NVME_HWMON) += hwmon.o +nvme-core-$(CONFIG_NVME_AUTH) += auth.o nvme-y += pci.o
drivers/nvme/host/auth.c new file +1169 -0
1,169 lines not on this page · raw message
drivers/nvme/host/auth.h new file +34 -0
@@ -0,0 +1,34 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright (c) 2021 Hannes Reinecke, SUSE Software Solutions +*/ + +#ifndef _NVME_AUTH_H +#define _NVME_AUTH_H + +#include <crypto/kpp.h> + +struct nvme_dhchap_key { +u8 *key; +size_t len; +u8 hash; +}; + +u32 nvme_auth_get_seqnum (void ); +const char *nvme_auth_dhgroup_name (u8 dhgroup_id); +size_t nvme_auth_dhgroup_pubkey_size (u8 dhgroup_id); +size_t nvme_auth_dhgroup_privkey_size (u8 dhgroup_id); +const char *nvme_auth_dhgroup_kpp (u8 dhgroup_id); +u8 nvme_auth_dhgroup_id (const char *dhgroup_name); + +const char *nvme_auth_hmac_name (u8 hmac_id); +const char *nvme_auth_digest_name (u8 hmac_id); +size_t nvme_auth_hmac_hash_len (u8 hmac_id); +u8 nvme_auth_hmac_id (const char *hmac_name); + +struct nvme_dhchap_key *nvme_auth_extract_key (unsigned char *secret, +u8 key_hash); +void nvme_auth_free_key (struct nvme_dhchap_key *key); +u8 *nvme_auth_transform_key (struct nvme_dhchap_key *key,char *nqn); + +#endif /* _NVME_AUTH_H */
drivers/nvme/host/core.c +137 -4
223 lines not on this page · raw message
drivers/nvme/host/fabrics.c +76 -3
134 lines not on this page · raw message
drivers/nvme/host/fabrics.h +7 -0
@@ -68,6 +68,8 @@ enum {NVMF_OPT_FAIL_FAST_TMO =1 <<20 ,NVMF_OPT_HOST_IFACE =1 <<21 ,NVMF_OPT_DISCOVERY =1 <<22 , +NVMF_OPT_DHCHAP_SECRET =1 <<23 , + NVMF_OPT_DHCHAP_CTRL_SECRET = 1 << 24, };/**
@@ -97,6 +99,9 @@ enum {* @max_reconnects: maximum number of allowed reconnect attempts before removing * the controller, (-1) means reconnect forever, zero means remove * immediately; +* @dhchap_secret: DH-HMAC-CHAP secret +* @dhchap_ctrl_secret: DH-HMAC-CHAP controller secret for bi-directional +* authentication * @disable_sqflow: disable controller sq flow control * @hdr_digest: generate/verify header digest (TCP) * @data_digest: generate/verify data digest (TCP)
@@ -121,6 +126,8 @@ struct nvmf_ctrl_options {unsigned int kato;struct nvmf_host *host;int max_reconnects; +char *dhchap_secret; +char *dhchap_ctrl_secret;bool disable_sqflow;bool hdr_digest;bool data_digest;
drivers/nvme/host/nvme.h +31 -0
@@ -324,6 +324,15 @@ struct nvme_ctrl {struct work_struct ana_work;#endif +#ifdef CONFIG_NVME_AUTH +struct work_struct dhchap_auth_work; +struct list_head dhchap_auth_list; +struct mutex dhchap_auth_mutex; +struct nvme_dhchap_key *host_key; +struct nvme_dhchap_key *ctrl_key; +u16 transaction; +#endif +/* Power saving configuration */ u64 ps_max_latency_us;bool apst_enabled;
@@ -910,6 +919,28 @@ static inline bool nvme_ctrl_sgl_supported(struct nvme_ctrl *ctrl)return ctrl->sgls & ((1 <<0 ) | (1 <<1 )); } +#ifdef CONFIG_NVME_AUTH +void nvme_auth_init_ctrl (struct nvme_ctrl *ctrl); +void nvme_auth_stop (struct nvme_ctrl *ctrl); +int nvme_auth_negotiate (struct nvme_ctrl *ctrl,int qid); +int nvme_auth_wait (struct nvme_ctrl *ctrl,int qid); +void nvme_auth_reset (struct nvme_ctrl *ctrl); +void nvme_auth_free (struct nvme_ctrl *ctrl); +int nvme_auth_generate_key (u8 *secret,struct nvme_dhchap_key **ret_key); +#else +static inline void nvme_auth_init_ctrl (struct nvme_ctrl *ctrl) {}; +static inline void nvme_auth_stop (struct nvme_ctrl *ctrl) {}; +static inline int nvme_auth_negotiate (struct nvme_ctrl *ctrl,int qid) +{ +return -EPROTONOSUPPORT ; +} +static inline int nvme_auth_wait (struct nvme_ctrl *ctrl,int qid) +{ +return NVME_SC_AUTH_REQUIRED ; +} +static inline void nvme_auth_free (struct nvme_ctrl *ctrl) {}; +#endif +u32 nvme_command_effects (struct nvme_ctrl *ctrl,struct nvme_ns *ns,u8 opcode);int nvme_execute_passthru_rq (struct request *rq);
drivers/nvme/host/rdma.c +1 -0
@@ -1199,6 +1199,7 @@ static void nvme_rdma_error_recovery_work(struct work_struct *work)struct nvme_rdma_ctrl *ctrl =container_of (work, struct nvme_rdma_ctrl, err_work); +nvme_auth_stop (&ctrl->ctrl);nvme_stop_keep_alive (&ctrl->ctrl);nvme_rdma_teardown_io_queues (ctrl, false);nvme_start_queues (&ctrl->ctrl);
drivers/nvme/host/tcp.c +1 -0
@@ -2096,6 +2096,7 @@ static void nvme_tcp_error_recovery_work(struct work_struct *work) struct nvme_tcp_ctrl, err_work);struct nvme_ctrl *ctrl = &tcp_ctrl->ctrl; +nvme_auth_stop (ctrl);nvme_stop_keep_alive (ctrl);nvme_tcp_teardown_io_queues (ctrl, false);/* unquiesce to fail fast pending requests */
drivers/nvme/host/trace.c +32 -0
@@ -287,6 +287,34 @@ static const char *nvme_trace_fabrics_property_get(struct trace_seq *p, u8 *spc)return ret; } +static const char *nvme_trace_fabrics_auth_send (struct trace_seq *p,u8 *spc) +{ +const char *ret =trace_seq_buffer_ptr (p); +u8 spsp0 = spc[1 ]; +u8 spsp1 = spc[2 ]; +u8 secp = spc[3 ]; +u32 tl =get_unaligned_le32 (spc +4 ); + +trace_seq_printf (p,"spsp0=%02x, spsp1=%02x, secp=%02x, tl=%u" , + spsp0, spsp1, secp, tl); +trace_seq_putc (p,0 ); +return ret; +} + +static const char *nvme_trace_fabrics_auth_receive (struct trace_seq *p,u8 *spc) +{ +const char *ret =trace_seq_buffer_ptr (p); +u8 spsp0 = spc[1 ]; +u8 spsp1 = spc[2 ]; +u8 secp = spc[3 ]; +u32 al =get_unaligned_le32 (spc +4 ); + +trace_seq_printf (p,"spsp0=%02x, spsp1=%02x, secp=%02x, al=%u" , + spsp0, spsp1, secp, al); +trace_seq_putc (p,0 ); +return ret; +} +static const char *nvme_trace_fabrics_common (struct trace_seq *p,u8 *spc) {const char *ret =trace_seq_buffer_ptr (p);
@@ -306,6 +334,10 @@ const char *nvme_trace_parse_fabrics_cmd(struct trace_seq *p,return nvme_trace_fabrics_connect (p, spc);case nvme_fabrics_type_property_get:return nvme_trace_fabrics_property_get (p, spc); +case nvme_fabrics_type_auth_send: +return nvme_trace_fabrics_auth_send (p, spc); +case nvme_fabrics_type_auth_receive: +return nvme_trace_fabrics_auth_receive (p, spc);default :return nvme_trace_fabrics_common (p, spc); }
Signature · 1 line
2.29.2
Re: [PATCH 07/12] nvme: Implement In-Band authentication
Hi Hannes,
Quoted 8 lines · Hannes Reinecke
Implement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds two new fabric options '
dhchap_secret' to specify the pre-shared key (in ASCII respresentation according to NVMe 2.0 section 8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specify the pre-shared controller key for bi-directional authentication of both the host and the controller.
Re-authentication can be triggered by writing the PSK into the new controller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.
Can you please add to commit log an example of the process ?
From target configuration through the 'nvme connect' cmd.
Quoted 936 lines
Signed-off-by Hannes Reinecke <[email protected]>--- drivers/nvme/host/Kconfig | 11 + drivers/nvme/host/Makefile | 1 + drivers/nvme/host/auth.c | 1169 +++++++++++++++++++++++++++++++++++ drivers/nvme/host/auth.h | 34 + drivers/nvme/host/core.c | 141 ++++- drivers/nvme/host/fabrics.c | 79 ++- drivers/nvme/host/fabrics.h | 7 + drivers/nvme/host/nvme.h | 31 + drivers/nvme/host/rdma.c | 1 + drivers/nvme/host/tcp.c | 1 + drivers/nvme/host/trace.c | 32 + 11 files changed, 1500 insertions(+), 7 deletions(-)create mode 100644
drivers/nvme/host/auth.c
create mode 100644drivers/nvme/host/auth.hdrivers/nvme/host/Kconfig +11
-0@@ -83,3 +83,14 @@ config NVME_TCP from https://github.com/linux-nvme/nvme-cli. If unsure, say N. + +config NVME_AUTH + bool "NVM Express over Fabrics In-Band Authentication" + depends on NVME_CORE + select CRYPTO_HMAC + select CRYPTO_SHA256 + select CRYPTO_SHA512 + help + This provides support for NVMe over Fabrics In-Band Authentication. + + If unsure, say N.drivers/nvme/host/Makefile +1
-0@@ -15,6 +15,7 @@ nvme-core-$(CONFIG_NVME_MULTIPATH) += multipath.o nvme-core-$(CONFIG_BLK_DEV_ZONED) += zns.o nvme-core-$(CONFIG_FAULT_INJECTION_DEBUG_FS) += fault_inject.o nvme-core-$(CONFIG_NVME_HWMON) += hwmon.o +nvme-core-$(CONFIG_NVME_AUTH) += auth.o nvme-y += pci.odrivers/nvme/host/auth.c new file +882
-0@@ -0,0 +1,1169 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* Copyright (c) 2020 Hannes Reinecke, SUSE Linux +*/ + +#include <linux/crc32.h> +#include <linux/base64.h> +#include <linux/prandom.h> +#include <asm/unaligned.h> +#include <crypto/hash.h> +#include <crypto/dh.h> +#include <crypto/ffdhe.h> +#include "nvme.h" +#include "fabrics.h" +#include "auth.h" + +static u32 nvme_dhchap_seqnum; +static DEFINE_MUTEX (nvme_dhchap_mutex); + +struct nvme_dhchap_queue_context { +struct list_head entry; +struct work_struct auth_work; +struct nvme_ctrl *ctrl; +struct crypto_shash *shash_tfm; +void *buf; +size_t buf_size; +int qid; +int error; +u32 s1; +u32 s2; +u16 transaction; +u8 status; +u8 hash_id; +size_t hash_len; +u8 dhgroup_id; +u8 c1[64 ]; +u8 c2[64 ]; +u8 response[64 ]; +u8 *host_response; +}; + +u32 nvme_auth_get_seqnum (void ) +{ +u32 seqnum; + +mutex_lock (&nvme_dhchap_mutex); +if (!nvme_dhchap_seqnum) + nvme_dhchap_seqnum =prandom_u32 (); +else { + nvme_dhchap_seqnum++; +if (!nvme_dhchap_seqnum) + nvme_dhchap_seqnum++; + } + seqnum = nvme_dhchap_seqnum; +mutex_unlock (&nvme_dhchap_mutex); +return seqnum; +} +EXPORT_SYMBOL_GPL (nvme_auth_get_seqnum); + +static struct nvme_auth_dhgroup_map { +u8 id; +const char name[16 ]; +const char kpp[16 ]; +size_t privkey_size; +size_t pubkey_size; +} dhgroup_map[] = { + { .id =NVME_AUTH_DHGROUP_NULL , + .name ="null" , .kpp ="null" , + .privkey_size =0 , .pubkey_size =0 }, + { .id =NVME_AUTH_DHGROUP_2048 , + .name ="ffdhe2048" , .kpp ="dh" , + .privkey_size =256 , .pubkey_size =256 }, + { .id =NVME_AUTH_DHGROUP_3072 , + .name ="ffdhe3072" , .kpp ="dh" , + .privkey_size =384 , .pubkey_size =384 }, + { .id =NVME_AUTH_DHGROUP_4096 , + .name ="ffdhe4096" , .kpp ="dh" , + .privkey_size =512 , .pubkey_size =512 }, + { .id =NVME_AUTH_DHGROUP_6144 , + .name ="ffdhe6144" , .kpp ="dh" , + .privkey_size =768 , .pubkey_size =768 }, + { .id =NVME_AUTH_DHGROUP_8192 , + .name ="ffdhe8192" , .kpp ="dh" , + .privkey_size =1024 , .pubkey_size =1024 }, +}; + +const char *nvme_auth_dhgroup_name (u8 dhgroup_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (dhgroup_map); i++) { +if (dhgroup_map[i].id == dhgroup_id) +return dhgroup_map[i].name; + } +return NULL ; +} +EXPORT_SYMBOL_GPL (nvme_auth_dhgroup_name); + +size_t nvme_auth_dhgroup_pubkey_size (u8 dhgroup_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (dhgroup_map); i++) { +if (dhgroup_map[i].id == dhgroup_id) +return dhgroup_map[i].pubkey_size; + } +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_auth_dhgroup_pubkey_size); + +size_t nvme_auth_dhgroup_privkey_size (u8 dhgroup_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (dhgroup_map); i++) { +if (dhgroup_map[i].id == dhgroup_id) +return dhgroup_map[i].privkey_size; + } +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_auth_dhgroup_privkey_size); + +const char *nvme_auth_dhgroup_kpp (u8 dhgroup_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (dhgroup_map); i++) { +if (dhgroup_map[i].id == dhgroup_id) +return dhgroup_map[i].kpp; + } +return NULL ; +} +EXPORT_SYMBOL_GPL (nvme_auth_dhgroup_kpp); + +u8 nvme_auth_dhgroup_id (const char *dhgroup_name) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (dhgroup_map); i++) { +if (!strncmp (dhgroup_map[i].name, dhgroup_name, +strlen (dhgroup_map[i].name))) +return dhgroup_map[i].id; + } +return NVME_AUTH_DHGROUP_INVALID ; +} +EXPORT_SYMBOL_GPL (nvme_auth_dhgroup_id); + +static struct nvme_dhchap_hash_map { +int id; +int len; +const char hmac[15 ]; +const char digest[15 ]; +} hash_map[] = { + {.id =NVME_AUTH_HASH_SHA256 , .len =32 , + .hmac ="hmac(sha256)" , .digest ="sha256" }, + {.id =NVME_AUTH_HASH_SHA384 , .len =48 , + .hmac ="hmac(sha384)" , .digest ="sha384" }, + {.id =NVME_AUTH_HASH_SHA512 , .len =64 , + .hmac ="hmac(sha512)" , .digest ="sha512" }, +}; + +const char *nvme_auth_hmac_name (u8 hmac_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (hash_map); i++) { +if (hash_map[i].id == hmac_id) +return hash_map[i].hmac; + } +return NULL ; +} +EXPORT_SYMBOL_GPL (nvme_auth_hmac_name); + +const char *nvme_auth_digest_name (u8 hmac_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (hash_map); i++) { +if (hash_map[i].id == hmac_id) +return hash_map[i].digest; + } +return NULL ; +} +EXPORT_SYMBOL_GPL (nvme_auth_digest_name); + +u8 nvme_auth_hmac_id (const char *hmac_name) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (hash_map); i++) { +if (!strncmp (hash_map[i].hmac, hmac_name, +strlen (hash_map[i].hmac))) +return hash_map[i].id; + } +return NVME_AUTH_HASH_INVALID ; +} +EXPORT_SYMBOL_GPL (nvme_auth_hmac_id); + +size_t nvme_auth_hmac_hash_len (u8 hmac_id) +{ +int i; + +for (i =0 ; i <ARRAY_SIZE (hash_map); i++) { +if (hash_map[i].id == hmac_id) +return hash_map[i].len; + } +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_auth_hmac_hash_len); + +struct nvme_dhchap_key *nvme_auth_extract_key (unsigned char *secret, +u8 key_hash) +{ +struct nvme_dhchap_key *key; +unsigned char *p; +u32 crc; +int ret, key_len; +size_t allocated_len =strlen (secret); + +/* Secret might be affixed with a ':' */ + p =strrchr (secret,':' ); +if (p) + allocated_len = p - secret; + key =kzalloc (sizeof (*key),GFP_KERNEL ); +if (!key) +return ERR_PTR (-ENOMEM ); + key->key =kzalloc (allocated_len,GFP_KERNEL ); +if (!key->key) { + ret = -ENOMEM ; + goto out_free_key; + } + + key_len =base64_decode (secret, allocated_len, key->key); +if (key_len <0 ) { +pr_debug ("base64 key decoding error %d\n" , + key_len); + ret = key_len; + goto out_free_secret; + } + +if (key_len !=36 && key_len !=52 && + key_len !=68 ) { +pr_err ("Invalid DH-HMAC-CHAP key len %d\n" , + key_len); + ret = -EINVAL ; + goto out_free_secret; + } + +if (key_hash >0 && + (key_len -4 ) !=nvme_auth_hmac_hash_len (key_hash)) { +pr_err ("Invalid DH-HMAC-CHAP key len %d for %s\n" , key_len, +nvme_auth_hmac_name (key_hash)); + ret = -EINVAL ; + goto out_free_secret; + } + +/* The last four bytes is the CRC in little-endian format */ + key_len -=4 ; +/* +* The linux implementation doesn't do pre- and post-increments, +* so we have to do it manually. +*/ + crc = ~crc32 (~0 , key->key, key_len); + +if (get_unaligned_le32 (key->key + key_len) != crc) { +pr_err ("DH-HMAC-CHAP key crc mismatch (key %08x, crc %08x)\n" , +get_unaligned_le32 (key->key + key_len), crc); + ret = -EKEYREJECTED ; + goto out_free_secret; + } + key->len = key_len; + key->hash = key_hash; +return key; +out_free_secret: +kfree_sensitive (key->key); +out_free_key: +kfree (key); +return ERR_PTR (ret); +} +EXPORT_SYMBOL_GPL (nvme_auth_extract_key); + +void nvme_auth_free_key (struct nvme_dhchap_key *key) +{ +if (!key) +return ; +kfree_sensitive (key->key); +kfree (key); +} +EXPORT_SYMBOL_GPL (nvme_auth_free_key); + +u8 *nvme_auth_transform_key (struct nvme_dhchap_key *key,char *nqn) +{ +const char *hmac_name =nvme_auth_hmac_name (key->hash); +struct crypto_shash *key_tfm; +struct shash_desc *shash; +u8 *transformed_key; +int ret; + +if (key->hash ==0 ) { + transformed_key =kmemdup (key->key, key->len,GFP_KERNEL ); +return transformed_key ? transformed_key :ERR_PTR (-ENOMEM ); + } + +if (!key || !key->key) { +pr_warn ("No key specified\n" ); +return ERR_PTR (-ENOKEY ); + } +if (!hmac_name) { +pr_warn ("Invalid key hash id %d\n" , key->hash); +return ERR_PTR (-EINVAL ); + } + + key_tfm =crypto_alloc_shash (hmac_name,0 ,0 ); +if (IS_ERR (key_tfm)) +return (u8 *)key_tfm; + + shash =kmalloc (sizeof (struct shash_desc ) + +crypto_shash_descsize (key_tfm), +GFP_KERNEL ); +if (!shash) { + ret = -ENOMEM ; + goto out_free_key; + } + + transformed_key =kzalloc (crypto_shash_digestsize (key_tfm),GFP_KERNEL ); +if (!transformed_key) { + ret = -ENOMEM ; + goto out_free_shash; + } + + shash->tfm = key_tfm; + ret =crypto_shash_setkey (key_tfm, key->key, key->len); +if (ret <0 ) + goto out_free_shash; + ret =crypto_shash_init (shash); +if (ret <0 ) + goto out_free_shash; + ret =crypto_shash_update (shash, nqn,strlen (nqn)); +if (ret <0 ) + goto out_free_shash; + ret =crypto_shash_update (shash,"NVMe-over-Fabrics" ,17 ); +if (ret <0 ) + goto out_free_shash; + ret =crypto_shash_final (shash, transformed_key); +out_free_shash: +kfree (shash); +out_free_key: +crypto_free_shash (key_tfm); +if (ret <0 ) { +kfree_sensitive (transformed_key); +return ERR_PTR (ret); + } +return transformed_key; +} +EXPORT_SYMBOL_GPL (nvme_auth_transform_key); + +#define nvme_auth_flags_from_qid (qid) \ + (qid == NVME_QID_ANY) ? 0 : BLK_MQ_REQ_NOWAIT | BLK_MQ_REQ_RESERVED +#define nvme_auth_queue_from_qid (ctrl, qid) \ + (qid == NVME_QID_ANY) ? (ctrl)->fabrics_q : (ctrl)->connect_q + +static int nvme_auth_send (struct nvme_ctrl *ctrl,int qid, +void *data,size_t tl) +{ +struct nvme_command cmd = {}; +blk_mq_req_flags_t flags =nvme_auth_flags_from_qid (qid); +struct request_queue *q =nvme_auth_queue_from_qid (ctrl, qid); +int ret; + + cmd.auth_send.opcode = nvme_fabrics_command; + cmd.auth_send.fctype = nvme_fabrics_type_auth_send; + cmd.auth_send.secp =NVME_AUTH_DHCHAP_PROTOCOL_IDENTIFIER ; + cmd.auth_send.spsp0 =0x01 ; + cmd.auth_send.spsp1 =0x01 ; + cmd.auth_send.tl =cpu_to_le32 (tl); + + ret =__nvme_submit_sync_cmd (q, &cmd,NULL , data, tl,0 , qid, +0 , flags); +if (ret >0 ) +dev_warn (ctrl->device, +"qid %d auth_send failed with status %d\n" , qid, ret); +else if (ret <0 ) +dev_err (ctrl->device, +"qid %d auth_send failed with error %d\n" , qid, ret); +return ret; +} + +static int nvme_auth_receive (struct nvme_ctrl *ctrl,int qid, +void *buf,size_t al) +{ +struct nvme_command cmd = {}; +blk_mq_req_flags_t flags =nvme_auth_flags_from_qid (qid); +struct request_queue *q =nvme_auth_queue_from_qid (ctrl, qid); +int ret; + + cmd.auth_receive.opcode = nvme_fabrics_command; + cmd.auth_receive.fctype = nvme_fabrics_type_auth_receive; + cmd.auth_receive.secp =NVME_AUTH_DHCHAP_PROTOCOL_IDENTIFIER ; + cmd.auth_receive.spsp0 =0x01 ; + cmd.auth_receive.spsp1 =0x01 ; + cmd.auth_receive.al =cpu_to_le32 (al); + + ret =__nvme_submit_sync_cmd (q, &cmd,NULL , buf, al,0 , qid, +0 , flags); +if (ret >0 ) { +dev_warn (ctrl->device, +"qid %d auth_recv failed with status %x\n" , qid, ret); + ret = -EIO ; + }else if (ret <0 ) { +dev_err (ctrl->device, +"qid %d auth_recv failed with error %d\n" , qid, ret); + } + +return ret; +} + +static int nvme_auth_receive_validate (struct nvme_ctrl *ctrl,int qid, +struct nvmf_auth_dhchap_failure_data *data, +u16 transaction,u8 expected_msg) +{ +dev_dbg (ctrl->device,"%s: qid %d auth_type %d auth_id %x\n" , + __func__, qid, data->auth_type, data->auth_id); + +if (data->auth_type ==NVME_AUTH_COMMON_MESSAGES && + data->auth_id ==NVME_AUTH_DHCHAP_MESSAGE_FAILURE1 ) { +return data->rescode_exp; + } +if (data->auth_type !=NVME_AUTH_DHCHAP_MESSAGES || + data->auth_id != expected_msg) { +dev_warn (ctrl->device, +"qid %d invalid message %02x/%02x\n" , + qid, data->auth_type, data->auth_id); +return NVME_AUTH_DHCHAP_FAILURE_INCORRECT_MESSAGE ; + } +if (le16_to_cpu (data->t_id) != transaction) { +dev_warn (ctrl->device, +"qid %d invalid transaction ID %d\n" , + qid,le16_to_cpu (data->t_id)); +return NVME_AUTH_DHCHAP_FAILURE_INCORRECT_MESSAGE ; + } +return 0 ; +} + +static int nvme_auth_set_dhchap_negotiate_data (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_negotiate_data *data = chap->buf; +size_t size =sizeof (*data) +sizeof (union nvmf_auth_protocol ); + +if (chap->buf_size < size) { + chap->status =NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD ; +return -EINVAL ; + } +memset ((u8 *)chap->buf,0 , size); + data->auth_type =NVME_AUTH_COMMON_MESSAGES ; + data->auth_id =NVME_AUTH_DHCHAP_MESSAGE_NEGOTIATE ; + data->t_id =cpu_to_le16 (chap->transaction); + data->sc_c =0 ;/* No secure channel concatenation */ + data->napd =1 ; + data->auth_protocol[0 ].dhchap.authid =NVME_AUTH_DHCHAP_AUTH_ID ; + data->auth_protocol[0 ].dhchap.halen =3 ; + data->auth_protocol[0 ].dhchap.dhlen =6 ; + data->auth_protocol[0 ].dhchap.idlist[0 ] =NVME_AUTH_HASH_SHA256 ; + data->auth_protocol[0 ].dhchap.idlist[1 ] =NVME_AUTH_HASH_SHA384 ; + data->auth_protocol[0 ].dhchap.idlist[2 ] =NVME_AUTH_HASH_SHA512 ; + data->auth_protocol[0 ].dhchap.idlist[30 ] =NVME_AUTH_DHGROUP_NULL ; + data->auth_protocol[0 ].dhchap.idlist[31 ] =NVME_AUTH_DHGROUP_2048 ; + data->auth_protocol[0 ].dhchap.idlist[32 ] =NVME_AUTH_DHGROUP_3072 ; + data->auth_protocol[0 ].dhchap.idlist[33 ] =NVME_AUTH_DHGROUP_4096 ; + data->auth_protocol[0 ].dhchap.idlist[34 ] =NVME_AUTH_DHGROUP_6144 ; + data->auth_protocol[0 ].dhchap.idlist[35 ] =NVME_AUTH_DHGROUP_8192 ; + +return size; +} + +static int nvme_auth_process_dhchap_challenge (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_challenge_data *data = chap->buf; +u16 dhvlen =le16_to_cpu (data->dhvlen); +size_t size =sizeof (*data) + data->hl + dhvlen; +const char *hmac_name, *kpp_name; + +if (chap->buf_size < size) { + chap->status =NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD ; +return NVME_SC_INVALID_FIELD ; + } + + hmac_name =nvme_auth_hmac_name (data->hashid); +if (!hmac_name) { +dev_warn (ctrl->device, +"qid %d: invalid HASH ID %d\n" , + chap->qid, data->hashid); + chap->status =NVME_AUTH_DHCHAP_FAILURE_HASH_UNUSABLE ; +return NVME_SC_INVALID_FIELD ; + } + +if (chap->hash_id == data->hashid && chap->shash_tfm && + !strcmp (crypto_shash_alg_name (chap->shash_tfm), hmac_name) && +crypto_shash_digestsize (chap->shash_tfm) == data->hl) { +dev_dbg (ctrl->device, +"qid %d: reuse existing hash %s\n" , + chap->qid, hmac_name); + goto select_kpp; + } + +/* Reset if hash cannot be reused */ +if (chap->shash_tfm) { +crypto_free_shash (chap->shash_tfm); + chap->hash_id =0 ; + chap->hash_len =0 ; + } + chap->shash_tfm =crypto_alloc_shash (hmac_name,0 , +CRYPTO_ALG_ALLOCATES_MEMORY ); +if (IS_ERR (chap->shash_tfm)) { +dev_warn (ctrl->device, +"qid %d: failed to allocate hash %s, error %ld\n" , + chap->qid, hmac_name,PTR_ERR (chap->shash_tfm)); + chap->shash_tfm =NULL ; + chap->status =NVME_AUTH_DHCHAP_FAILURE_FAILED ; +return NVME_SC_AUTH_REQUIRED ; + } + +if (crypto_shash_digestsize (chap->shash_tfm) != data->hl) { +dev_warn (ctrl->device, +"qid %d: invalid hash length %d\n" , + chap->qid, data->hl); +crypto_free_shash (chap->shash_tfm); + chap->shash_tfm =NULL ; + chap->status =NVME_AUTH_DHCHAP_FAILURE_HASH_UNUSABLE ; +return NVME_SC_AUTH_REQUIRED ; + } + +/* Reset host response if the hash had been changed */ +if (chap->hash_id != data->hashid) { +kfree (chap->host_response); + chap->host_response =NULL ; + } + + chap->hash_id = data->hashid; + chap->hash_len = data->hl; +dev_dbg (ctrl->device,"qid %d: selected hash %s\n" , + chap->qid, hmac_name); + +select_kpp: + kpp_name =nvme_auth_dhgroup_kpp (data->dhgid); +if (!kpp_name) { +dev_warn (ctrl->device, +"qid %d: invalid DH group id %d\n" , + chap->qid, data->dhgid); + chap->status =NVME_AUTH_DHCHAP_FAILURE_DHGROUP_UNUSABLE ; +return NVME_SC_AUTH_REQUIRED ; + } + +if (data->dhgid !=NVME_AUTH_DHGROUP_NULL ) { +dev_warn (ctrl->device, +"qid %d: unsupported DH group %s\n" , + chap->qid, kpp_name); + chap->status =NVME_AUTH_DHCHAP_FAILURE_DHGROUP_UNUSABLE ; +return NVME_SC_AUTH_REQUIRED ; + }else if (dhvlen !=0 ) { +dev_warn (ctrl->device, +"qid %d: invalid DH value for NULL DH\n" , + chap->qid); + chap->status =NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD ; +return NVME_SC_INVALID_FIELD ; + } + chap->dhgroup_id = data->dhgid; + + chap->s1 =le32_to_cpu (data->seqnum); +memcpy (chap->c1, data->cval, chap->hash_len); + +return 0 ; +} + +static int nvme_auth_set_dhchap_reply_data (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_reply_data *data = chap->buf; +size_t size =sizeof (*data); + + size +=2 * chap->hash_len; + +if (chap->buf_size < size) { + chap->status =NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD ; +return -EINVAL ; + } + +memset (chap->buf,0 , size); + data->auth_type =NVME_AUTH_DHCHAP_MESSAGES ; + data->auth_id =NVME_AUTH_DHCHAP_MESSAGE_REPLY ; + data->t_id =cpu_to_le16 (chap->transaction); + data->hl = chap->hash_len; + data->dhvlen =0 ; +memcpy (data->rval, chap->response, chap->hash_len); +if (ctrl->opts->dhchap_ctrl_secret) { +get_random_bytes (chap->c2, chap->hash_len); + data->cvalid =1 ; + chap->s2 =nvme_auth_get_seqnum (); +memcpy (data->rval + chap->hash_len, chap->c2, + chap->hash_len); +dev_dbg (ctrl->device,"%s: qid %d ctrl challenge %*ph\n" , + __func__, chap->qid, (int )chap->hash_len, chap->c2); + }else { +memset (chap->c2,0 , chap->hash_len); + chap->s2 =0 ; + } + data->seqnum =cpu_to_le32 (chap->s2); +return size; +} + +static int nvme_auth_process_dhchap_success1 (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_success1_data *data = chap->buf; +size_t size =sizeof (*data); + +if (ctrl->opts->dhchap_ctrl_secret) + size += chap->hash_len; + +if (chap->buf_size < size) { + chap->status =NVME_AUTH_DHCHAP_FAILURE_INCORRECT_PAYLOAD ; +return NVME_SC_INVALID_FIELD ; + } + +if (data->hl != chap->hash_len) { +dev_warn (ctrl->device, +"qid %d: invalid hash length %u\n" , + chap->qid, data->hl); + chap->status =NVME_AUTH_DHCHAP_FAILURE_HASH_UNUSABLE ; +return NVME_SC_INVALID_FIELD ; + } + +/* Just print out information for the admin queue */ +if (chap->qid ==-1 ) +dev_info (ctrl->device, +"qid 0: authenticated with hash %s dhgroup %s\n" , +nvme_auth_hmac_name (chap->hash_id), +nvme_auth_dhgroup_name (chap->dhgroup_id)); + +if (!data->rvalid) +return 0 ; + +/* Validate controller response */ +if (memcmp (chap->response, data->rval, data->hl)) { +dev_dbg (ctrl->device,"%s: qid %d ctrl response %*ph\n" , + __func__, chap->qid, (int )chap->hash_len, data->rval); +dev_dbg (ctrl->device,"%s: qid %d host response %*ph\n" , + __func__, chap->qid, (int )chap->hash_len, + chap->response); +dev_warn (ctrl->device, +"qid %d: controller authentication failed\n" , + chap->qid); + chap->status =NVME_AUTH_DHCHAP_FAILURE_FAILED ; +return NVME_SC_AUTH_REQUIRED ; + } + +/* Just print out information for the admin queue */ +if (chap->qid ==-1 ) +dev_info (ctrl->device, +"qid 0: controller authenticated\n" ); +return 0 ; +} + +static int nvme_auth_set_dhchap_success2_data (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_success2_data *data = chap->buf; +size_t size =sizeof (*data); + +memset (chap->buf,0 , size); + data->auth_type =NVME_AUTH_DHCHAP_MESSAGES ; + data->auth_id =NVME_AUTH_DHCHAP_MESSAGE_SUCCESS2 ; + data->t_id =cpu_to_le16 (chap->transaction); + +return size; +} + +static int nvme_auth_set_dhchap_failure2_data (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +struct nvmf_auth_dhchap_failure_data *data = chap->buf; +size_t size =sizeof (*data); + +memset (chap->buf,0 , size); + data->auth_type =NVME_AUTH_DHCHAP_MESSAGES ; + data->auth_id =NVME_AUTH_DHCHAP_MESSAGE_FAILURE2 ; + data->t_id =cpu_to_le16 (chap->transaction); + data->rescode =NVME_AUTH_DHCHAP_FAILURE_REASON_FAILED ; + data->rescode_exp = chap->status; + +return size; +} + +static int nvme_auth_dhchap_setup_host_response (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +SHASH_DESC_ON_STACK (shash, chap->shash_tfm); +u8 buf[4 ], *challenge = chap->c1; +int ret; + +dev_dbg (ctrl->device,"%s: qid %d host response seq %u transaction %d\n" , + __func__, chap->qid, chap->s1, chap->transaction); + +if (!chap->host_response) { + chap->host_response =nvme_auth_transform_key (ctrl->host_key, + ctrl->opts->host->nqn); +if (IS_ERR (chap->host_response)) { + ret =PTR_ERR (chap->host_response); + chap->host_response =NULL ; +return ret; + } + }else { +dev_dbg (ctrl->device,"%s: qid %d re-using host response\n" , + __func__, chap->qid); + } + + ret =crypto_shash_setkey (chap->shash_tfm, + chap->host_response, ctrl->host_key->len); +if (ret) { +dev_warn (ctrl->device,"qid %d: failed to set key, error %d\n" , + chap->qid, ret); + goto out; + } + + shash->tfm = chap->shash_tfm; + ret =crypto_shash_init (shash); +if (ret) + goto out; + ret =crypto_shash_update (shash, challenge, chap->hash_len); +if (ret) + goto out; +put_unaligned_le32 (chap->s1, buf); + ret =crypto_shash_update (shash, buf,4 ); +if (ret) + goto out; +put_unaligned_le16 (chap->transaction, buf); + ret =crypto_shash_update (shash, buf,2 ); +if (ret) + goto out; +memset (buf,0 ,sizeof (buf)); + ret =crypto_shash_update (shash, buf,1 ); +if (ret) + goto out; + ret =crypto_shash_update (shash,"HostHost" ,8 ); +if (ret) + goto out; + ret =crypto_shash_update (shash, ctrl->opts->host->nqn, +strlen (ctrl->opts->host->nqn)); +if (ret) + goto out; + ret =crypto_shash_update (shash, buf,1 ); +if (ret) + goto out; + ret =crypto_shash_update (shash, ctrl->opts->subsysnqn, +strlen (ctrl->opts->subsysnqn)); +if (ret) + goto out; + ret =crypto_shash_final (shash, chap->response); +out: +if (challenge != chap->c1) +kfree (challenge); +return ret; +} + +static int nvme_auth_dhchap_setup_ctrl_response (struct nvme_ctrl *ctrl, +struct nvme_dhchap_queue_context *chap) +{ +SHASH_DESC_ON_STACK (shash, chap->shash_tfm); +u8 *ctrl_response; +u8 buf[4 ], *challenge = chap->c2; +int ret; + + ctrl_response =nvme_auth_transform_key (ctrl->ctrl_key, + ctrl->opts->subsysnqn); +if (IS_ERR (ctrl_response)) { + ret =PTR_ERR (ctrl_response); +return ret; + } + ret =crypto_shash_setkey (chap->shash_tfm, + ctrl_response, ctrl->ctrl_key->len); +if (ret) { +dev_warn (ctrl->device,"qid %d: failed to set key, error %d\n" , + chap->qid, ret); + goto out; + } + +dev_dbg (ctrl->device,"%s: qid %d ctrl response seq %u transaction %d\n" , + __func__, chap->qid, chap->s2, chap->transaction); +dev_dbg (ctrl->device,"%s: qid %d challenge %*ph\n" , + __func__, chap->qid, (int )chap->hash_len, challenge); +dev_dbg (ctrl->device,"%s: qid %d subsysnqn %s\n" , + __func__, chap->qid, ctrl->opts->subsysnqn); +dev_dbg (ctrl->device,"%s: qid %d hostnqn %s\n" , + __func__, chap->qid, ctrl->opts->host->nqn); + shash->tfm = chap->shash_tfm; + ret =crypto_shash_init (shash); +if (ret) + goto out; + ret =crypto_shash_update (shash, challenge, chap->hash_len); +if (ret) + goto out; +put_unaligned_le32 (chap->s2, buf); + ret =crypto_shash_update (shash, buf,4 ); +if (ret) + goto out; +put_unaligned_le16 (chap->transaction, buf); + ret =crypto_shash_update (shash, buf,2 ); +if (ret) + goto out; +memset (buf,0 ,4 ); + ret =crypto_shash_update (shash, buf,1 ); +if (ret) + goto out; + ret =crypto_shash_update (shash,"Controller" ,10 ); +if (ret) + goto out; + ret =crypto_shash_update (shash, ctrl->opts->subsysnqn, +strlen (ctrl->opts->subsysnqn)); +if (ret) + goto out; + ret =crypto_shash_update (shash, buf,1 ); +if (ret) + goto out; + ret =crypto_shash_update (shash, ctrl->opts->host->nqn, +strlen (ctrl->opts->host->nqn)); +if (ret) + goto out; + ret =crypto_shash_final (shash, chap->response); +out: +if (challenge != chap->c2) +kfree (challenge); +return ret; +} + +int nvme_auth_generate_key (u8 *secret,struct nvme_dhchap_key **ret_key) +{ +struct nvme_dhchap_key *key; +u8 key_hash; + +if (!secret) { + *ret_key =NULL ; +return 0 ; + } + +if (sscanf (secret,"DHHC-1:%hhd:%*s:" , &key_hash) !=1 ) +return -EINVAL ; + +/* Pass in the secret without the 'DHHC-1:XX:' prefix */ + key =nvme_auth_extract_key (secret +10 , key_hash); +if (IS_ERR (key)) { +return PTR_ERR (key); + } + + *ret_key = key; +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_auth_generate_key); + +static void __nvme_auth_reset (struct nvme_dhchap_queue_context *chap) +{ + chap->status =0 ; + chap->error =0 ; + chap->s1 =0 ; + chap->s2 =0 ; + chap->transaction =0 ; +memset (chap->c1,0 ,sizeof (chap->c1)); +memset (chap->c2,0 ,sizeof (chap->c2)); +} + +static void __nvme_auth_free (struct nvme_dhchap_queue_context *chap) +{ +if (chap->shash_tfm) +crypto_free_shash (chap->shash_tfm); +kfree_sensitive (chap->host_response); +kfree (chap->buf); +kfree (chap); +} + +static void __nvme_auth_work (struct work_struct *work) +{ + struct nvme_dhchap_queue_context *chap =
drivers/nvme/host/auth.c line 892
Quoted 10 lines
drivers/nvme/host/auth.c new file +10
-0+ container_of(work, struct nvme_dhchap_queue_context, auth_work); +struct nvme_ctrl *ctrl = chap->ctrl; +size_t tl; +int ret =0 ; + + chap->transaction = ctrl->transaction++; + +/* DH-HMAC-CHAP Step 1: send negotiate */ +dev_dbg (ctrl->device,"%s: qid %d send negotiate\n" , + __func__, chap->qid);
maybe you can use a local variable for ctrl->device
Quoted 208 lines
drivers/nvme/host/auth.c new file +208
-0+ ret =nvme_auth_set_dhchap_negotiate_data (ctrl, chap); +if (ret <0 ) { + chap->error = ret; +return ; + } + tl = ret; + ret =nvme_auth_send (ctrl, chap->qid, chap->buf, tl); +if (ret) { + chap->error = ret; +return ; + } + +/* DH-HMAC-CHAP Step 2: receive challenge */ +dev_dbg (ctrl->device,"%s: qid %d receive challenge\n" , + __func__, chap->qid); + +memset (chap->buf,0 , chap->buf_size); + ret =nvme_auth_receive (ctrl, chap->qid, chap->buf, chap->buf_size); +if (ret) { +dev_warn (ctrl->device, +"qid %d failed to receive challenge, %s %d\n" , + chap->qid, ret <0 ?"error" :"nvme status" , ret); + chap->error = ret; +return ; + } + ret =nvme_auth_receive_validate (ctrl, chap->qid, chap->buf, chap->transaction, +NVME_AUTH_DHCHAP_MESSAGE_CHALLENGE ); +if (ret) { + chap->status = ret; + chap->error =NVME_SC_AUTH_REQUIRED ; +return ; + } + + ret =nvme_auth_process_dhchap_challenge (ctrl, chap); +if (ret) { +/* Invalid challenge parameters */ + goto fail2; + } + +dev_dbg (ctrl->device,"%s: qid %d host response\n" , + __func__, chap->qid); + ret =nvme_auth_dhchap_setup_host_response (ctrl, chap); +if (ret) + goto fail2; + +/* DH-HMAC-CHAP Step 3: send reply */ +dev_dbg (ctrl->device,"%s: qid %d send reply\n" , + __func__, chap->qid); + ret =nvme_auth_set_dhchap_reply_data (ctrl, chap); +if (ret <0 ) + goto fail2; + + tl = ret; + ret =nvme_auth_send (ctrl, chap->qid, chap->buf, tl); +if (ret) + goto fail2; + +/* DH-HMAC-CHAP Step 4: receive success1 */ +dev_dbg (ctrl->device,"%s: qid %d receive success1\n" , + __func__, chap->qid); + +memset (chap->buf,0 , chap->buf_size); + ret =nvme_auth_receive (ctrl, chap->qid, chap->buf, chap->buf_size); +if (ret) { +dev_warn (ctrl->device, +"qid %d failed to receive success1, %s %d\n" , + chap->qid, ret <0 ?"error" :"nvme status" , ret); + chap->error = ret; +return ; + } + ret =nvme_auth_receive_validate (ctrl, chap->qid, + chap->buf, chap->transaction, +NVME_AUTH_DHCHAP_MESSAGE_SUCCESS1 ); +if (ret) { + chap->status = ret; + chap->error =NVME_SC_AUTH_REQUIRED ; +return ; + } + +if (ctrl->opts->dhchap_ctrl_secret) { +dev_dbg (ctrl->device, +"%s: qid %d controller response\n" , + __func__, chap->qid); + ret =nvme_auth_dhchap_setup_ctrl_response (ctrl, chap); +if (ret) + goto fail2; + } + + ret =nvme_auth_process_dhchap_success1 (ctrl, chap); +if (ret) { +/* Controller authentication failed */ + goto fail2; + } + +/* DH-HMAC-CHAP Step 5: send success2 */ +dev_dbg (ctrl->device,"%s: qid %d send success2\n" , + __func__, chap->qid); + tl =nvme_auth_set_dhchap_success2_data (ctrl, chap); + ret =nvme_auth_send (ctrl, chap->qid, chap->buf, tl); +if (!ret) { + chap->error =0 ; +return ; + } + +fail2: +dev_dbg (ctrl->device,"%s: qid %d send failure2, status %x\n" , + __func__, chap->qid, chap->status); + tl =nvme_auth_set_dhchap_failure2_data (ctrl, chap); + ret =nvme_auth_send (ctrl, chap->qid, chap->buf, tl); +if (!ret) + ret = -EPROTO ; + chap->error = ret; +} + +int nvme_auth_negotiate (struct nvme_ctrl *ctrl,int qid) +{ +struct nvme_dhchap_queue_context *chap; + +if (!ctrl->host_key) { +dev_warn (ctrl->device,"qid %d: no key\n" , qid); +return -ENOKEY ; + } + +mutex_lock (&ctrl->dhchap_auth_mutex); +/* Check if the context is already queued */ +list_for_each_entry (chap, &ctrl->dhchap_auth_list, entry) { +WARN_ON (!chap->buf); +if (chap->qid == qid) { +dev_dbg (ctrl->device,"qid %d: re-using context\n" , qid); +mutex_unlock (&ctrl->dhchap_auth_mutex); +flush_work (&chap->auth_work); +__nvme_auth_reset (chap); +queue_work (nvme_wq, &chap->auth_work); +return 0 ; + } + } + chap =kzalloc (sizeof (*chap),GFP_KERNEL ); +if (!chap) { +mutex_unlock (&ctrl->dhchap_auth_mutex); +return -ENOMEM ; + } + chap->qid = qid; + chap->ctrl = ctrl; + +/* +* Allocate a large enough buffer for the entire negotiation: +* 4k should be enough to ffdhe8192. +*/ + chap->buf_size =4096 ; + chap->buf =kzalloc (chap->buf_size,GFP_KERNEL ); +if (!chap->buf) { +mutex_unlock (&ctrl->dhchap_auth_mutex); +kfree (chap); +return -ENOMEM ; + } + +INIT_WORK (&chap->auth_work, __nvme_auth_work); +list_add (&chap->entry, &ctrl->dhchap_auth_list); +mutex_unlock (&ctrl->dhchap_auth_mutex); +queue_work (nvme_wq, &chap->auth_work); +return 0 ; +} +EXPORT_SYMBOL_GPL (nvme_auth_negotiate); + +int nvme_auth_wait (struct nvme_ctrl *ctrl,int qid) +{ +struct nvme_dhchap_queue_context *chap; +int ret; + +mutex_lock (&ctrl->dhchap_auth_mutex); +list_for_each_entry (chap, &ctrl->dhchap_auth_list, entry) { +if (chap->qid != qid) +continue ; +mutex_unlock (&ctrl->dhchap_auth_mutex); +flush_work (&chap->auth_work); + ret = chap->error; +__nvme_auth_reset (chap); +return ret; + } +mutex_unlock (&ctrl->dhchap_auth_mutex); +return -ENXIO ; +} +EXPORT_SYMBOL_GPL (nvme_auth_wait); + +void nvme_auth_reset (struct nvme_ctrl *ctrl) +{ +struct nvme_dhchap_queue_context *chap; + +mutex_lock (&ctrl->dhchap_auth_mutex); +list_for_each_entry (chap, &ctrl->dhchap_auth_list, entry) { +mutex_unlock (&ctrl->dhchap_auth_mutex); +flush_work (&chap->auth_work); +__nvme_auth_reset (chap); + } +mutex_unlock (&ctrl->dhchap_auth_mutex); +} +EXPORT_SYMBOL_GPL (nvme_auth_reset); + +static void nvme_dhchap_auth_work (struct work_struct *work) +{ +struct nvme_ctrl *ctrl = + container_of(work, struct nvme_ctrl, dhchap_auth_work); +int ret, q; + +/* Authenticate admin queue first */ + ret =nvme_auth_negotiate (ctrl,NVME_QID_ANY ); +if (ret) { + dev_warn(ctrl->device,
drivers/nvme/host/auth.c line 1110
Quoted 10 lines
drivers/nvme/host/auth.c new file +10
-0+ "qid 0: error %d setting up authentication\n", ret); +return ; + } + ret =nvme_auth_wait (ctrl,NVME_QID_ANY ); +if (ret) { +dev_warn (ctrl->device, +"qid 0: authentication failed\n" ); +return ; + } +
maybe add a comment /* Authenticate IO queues */
drivers/nvme/host/auth.c line 1118
Quoted 8 lines
drivers/nvme/host/auth.c new file +8
-0+for (q =1 ; q < ctrl->queue_count; q++) { + ret =nvme_auth_negotiate (ctrl, q); +if (ret) { +dev_warn (ctrl->device, +"qid %d: error %d setting up authentication\n" , + q, ret); +break ; + }
shouldn't we wait for nvme_auth_wait ?
Quoted 193 lines
drivers/nvme/host/auth.c new file +51
-0+ } + +/* +* Failure is a soft-state; credentials remain valid until +* the controller terminates the connection. +*/ +} + +void nvme_auth_init_ctrl (struct nvme_ctrl *ctrl) +{ +INIT_LIST_HEAD (&ctrl->dhchap_auth_list); +INIT_WORK (&ctrl->dhchap_auth_work, nvme_dhchap_auth_work); +mutex_init (&ctrl->dhchap_auth_mutex); +nvme_auth_generate_key (ctrl->opts->dhchap_secret, &ctrl->host_key); +nvme_auth_generate_key (ctrl->opts->dhchap_ctrl_secret, &ctrl->ctrl_key); +} +EXPORT_SYMBOL_GPL (nvme_auth_init_ctrl); + +void nvme_auth_stop (struct nvme_ctrl *ctrl) +{ +struct nvme_dhchap_queue_context *chap =NULL , *tmp; + +cancel_work_sync (&ctrl->dhchap_auth_work); +mutex_lock (&ctrl->dhchap_auth_mutex); +list_for_each_entry_safe (chap, tmp, &ctrl->dhchap_auth_list, entry) +cancel_work_sync (&chap->auth_work); +mutex_unlock (&ctrl->dhchap_auth_mutex); +} +EXPORT_SYMBOL_GPL (nvme_auth_stop); + +void nvme_auth_free (struct nvme_ctrl *ctrl) +{ +struct nvme_dhchap_queue_context *chap =NULL , *tmp; + +mutex_lock (&ctrl->dhchap_auth_mutex); +list_for_each_entry_safe (chap, tmp, &ctrl->dhchap_auth_list, entry) { +list_del_init (&chap->entry); +flush_work (&chap->auth_work); +__nvme_auth_free (chap); + } +mutex_unlock (&ctrl->dhchap_auth_mutex); +if (ctrl->host_key) { +nvme_auth_free_key (ctrl->host_key); + ctrl->host_key =NULL ; + } +if (ctrl->ctrl_key) { +nvme_auth_free_key (ctrl->ctrl_key); + ctrl->ctrl_key =NULL ; + } +} +EXPORT_SYMBOL_GPL (nvme_auth_free);drivers/nvme/host/auth.h new file +34
-0@@ -0,0 +1,34 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright (c) 2021 Hannes Reinecke, SUSE Software Solutions +*/ + +#ifndef _NVME_AUTH_H +#define _NVME_AUTH_H + +#include <crypto/kpp.h> + +struct nvme_dhchap_key { +u8 *key; +size_t len; +u8 hash; +}; + +u32 nvme_auth_get_seqnum (void ); +const char *nvme_auth_dhgroup_name (u8 dhgroup_id); +size_t nvme_auth_dhgroup_pubkey_size (u8 dhgroup_id); +size_t nvme_auth_dhgroup_privkey_size (u8 dhgroup_id); +const char *nvme_auth_dhgroup_kpp (u8 dhgroup_id); +u8 nvme_auth_dhgroup_id (const char *dhgroup_name); + +const char *nvme_auth_hmac_name (u8 hmac_id); +const char *nvme_auth_digest_name (u8 hmac_id); +size_t nvme_auth_hmac_hash_len (u8 hmac_id); +u8 nvme_auth_hmac_id (const char *hmac_name); + +struct nvme_dhchap_key *nvme_auth_extract_key (unsigned char *secret, +u8 key_hash); +void nvme_auth_free_key (struct nvme_dhchap_key *key); +u8 *nvme_auth_transform_key (struct nvme_dhchap_key *key,char *nqn); + +#endif /* _NVME_AUTH_H */ drivers/nvme/host/core.c +46
-3@@ -24,6 +24,7 @@#include "nvme.h" #include "fabrics.h" +#include "auth.h" #define CREATE_TRACE_POINTS #include "trace.h" @@ -303,6 +304,7 @@ enum nvme_disposition {COMPLETE ,RETRY ,FAILOVER , + AUTHENTICATE, };static inline enum nvme_disposition nvme_decide_disposition (struct request *req)@@ -310,6 +312,9 @@ static inline enum nvme_disposition nvme_decide_disposition(struct request *req)if (likely (nvme_req (req)->status ==0 ))return COMPLETE ; +if ((nvme_req (req)->status &0x7ff ) ==NVME_SC_AUTH_REQUIRED ) +return AUTHENTICATE ; +if (blk_noretry_request (req) || (nvme_req (req)->status &NVME_SC_DNR ) ||nvme_req (req)->retries >= nvme_max_retries)@@ -346,11 +351,13 @@ static inline void nvme_end_req(struct request *req)void nvme_complete_rq (struct request *req) { +struct nvme_ctrl *ctrl =nvme_req (req)->ctrl; +trace_nvme_complete_rq (req);nvme_cleanup_cmd (req); -if (nvme_req (req)->ctrl->kas) -nvme_req (req)->ctrl->comp_seen = true; +if (ctrl->kas) + ctrl->comp_seen = true;switch (nvme_decide_disposition (req)) {case COMPLETE :@@ -362,6 +369,14 @@ void nvme_complete_rq(struct request *req)case FAILOVER :nvme_failover_req (req);return ; +case AUTHENTICATE : +#ifdef CONFIG_NVME_AUTH +queue_work (nvme_wq, &ctrl->dhchap_auth_work); +nvme_retry_req (req); +#else +nvme_end_req (req); +#endif +return ; } }EXPORT_SYMBOL_GPL (nvme_complete_rq);@@ -699,7 +714,9 @@ bool __nvme_check_ready(struct nvme_ctrl *ctrl, struct request *rq,switch (ctrl->state) {case NVME_CTRL_CONNECTING :if (blk_rq_is_passthrough (rq) &&nvme_is_fabrics (req->cmd) && - req->cmd->fabrics.fctype == nvme_fabrics_type_connect) + (req->cmd->fabrics.fctype == nvme_fabrics_type_connect || + req->cmd->fabrics.fctype == nvme_fabrics_type_auth_send || + req->cmd->fabrics.fctype == nvme_fabrics_type_auth_receive))return true;break ;default :@@ -3494,6 +3511,108 @@ static ssize_t nvme_ctrl_fast_io_fail_tmo_store(struct device *dev, static DEVICE_ATTR(fast_io_fail_tmo, S_IRUGO | S_IWUSR, nvme_ctrl_fast_io_fail_tmo_show, nvme_ctrl_fast_io_fail_tmo_store); +#ifdef CONFIG_NVME_AUTH +static ssize_t nvme_ctrl_dhchap_secret_show (struct device *dev, +struct device_attribute *attr,char *buf) +{ +struct nvme_ctrl *ctrl =dev_get_drvdata (dev); +struct nvmf_ctrl_options *opts = ctrl->opts; + +if (!opts->dhchap_secret) +return sysfs_emit (buf,"none\n" ); +return sysfs_emit (buf,"%s\n" , opts->dhchap_secret); +} + +static ssize_t nvme_ctrl_dhchap_secret_store (struct device *dev, +struct device_attribute *attr,const char *buf,size_t count) +{ +struct nvme_ctrl *ctrl =dev_get_drvdata (dev); +struct nvmf_ctrl_options *opts = ctrl->opts; +char *dhchap_secret; + +if (!ctrl->opts->dhchap_secret) +return -EINVAL ; +if (count <7 ) +return -EINVAL ; +if (memcmp (buf,"DHHC-1:" ,7 )) +return -EINVAL ; +
drivers/nvme/host/core.c static ssize_t nvme_ctrl_fast_io_fail_tmo_store(struct device *dev, · line 3549
Quoted 10 lines
drivers/nvme/host/core.c +10
-0+ dhchap_secret =kzalloc (count +1 ,GFP_KERNEL ); +if (!dhchap_secret) +return -ENOMEM ; +memcpy (dhchap_secret, buf, count); +nvme_auth_stop (ctrl); +if (strcmp (dhchap_secret, opts->dhchap_secret)) { +int ret; + + ret =nvme_auth_generate_key (dhchap_secret, &ctrl->host_key); +if (ret)
shouldn't we free dhchap_secret ?
Quoted 40 lines
drivers/nvme/host/core.c +40
-0+return ret; +kfree (opts->dhchap_secret); + opts->dhchap_secret = dhchap_secret; +/* Key has changed; re-authentication with new key */ +nvme_auth_reset (ctrl); + } +/* Start re-authentication */ +dev_info (ctrl->device,"re-authenticating controller\n" ); +queue_work (nvme_wq, &ctrl->dhchap_auth_work); + +return count; +} +DEVICE_ATTR (dhchap_secret,S_IRUGO |S_IWUSR , + nvme_ctrl_dhchap_secret_show, nvme_ctrl_dhchap_secret_store); + +static ssize_t nvme_ctrl_dhchap_ctrl_secret_show (struct device *dev, +struct device_attribute *attr,char *buf) +{ +struct nvme_ctrl *ctrl =dev_get_drvdata (dev); +struct nvmf_ctrl_options *opts = ctrl->opts; + +if (!opts->dhchap_ctrl_secret) +return sysfs_emit (buf,"none\n" ); +return sysfs_emit (buf,"%s\n" , opts->dhchap_ctrl_secret); +} + +static ssize_t nvme_ctrl_dhchap_ctrl_secret_store (struct device *dev, +struct device_attribute *attr,const char *buf,size_t count) +{ +struct nvme_ctrl *ctrl =dev_get_drvdata (dev); +struct nvmf_ctrl_options *opts = ctrl->opts; +char *dhchap_secret; + +if (!ctrl->opts->dhchap_ctrl_secret) +return -EINVAL ; +if (count <7 ) +return -EINVAL ; +if (memcmp (buf,"DHHC-1:" ,7 )) +return -EINVAL ; +
drivers/nvme/host/core.c static ssize_t nvme_ctrl_fast_io_fail_tmo_store(struct device *dev, · line 3599
Quoted 10 lines
drivers/nvme/host/core.c +10
-0+ dhchap_secret =kzalloc (count +1 ,GFP_KERNEL ); +if (!dhchap_secret) +return -ENOMEM ; +memcpy (dhchap_secret, buf, count); +nvme_auth_stop (ctrl); +if (strcmp (dhchap_secret, opts->dhchap_ctrl_secret)) { +int ret; + + ret =nvme_auth_generate_key (dhchap_secret, &ctrl->ctrl_key); +if (ret)
same free here.
Quoted 20 lines
drivers/nvme/host/core.c +16
-0+return ret; +kfree (opts->dhchap_ctrl_secret); + opts->dhchap_ctrl_secret = dhchap_secret; +/* Key has changed; re-authentication with new key */ + nvme_auth_reset(ctrl); + } +/* Start re-authentication */ +dev_info (ctrl->device,"re-authenticating controller\n" ); +queue_work (nvme_wq, &ctrl->dhchap_auth_work); + +return count; +} +DEVICE_ATTR (dhchap_ctrl_secret,S_IRUGO |S_IWUSR , + nvme_ctrl_dhchap_ctrl_secret_show, nvme_ctrl_dhchap_ctrl_secret_store); +#endif +static struct attribute *nvme_dev_attrs[] = { &dev_attr_reset_controller.attr, &dev_attr_rescan_controller.attr,
drivers/nvme/host/core.c static struct attribute *nvme_dev_attrs[] = { · line 3640
Quoted 7 lines
drivers/nvme/host/core.c +4
-0@@ -3515,6 +3634,10 @@ static struct attribute *nvme_dev_attrs[] = { &dev_attr_reconnect_delay.attr, &dev_attr_fast_io_fail_tmo.attr, &dev_attr_kato.attr, +#ifdef CONFIG_NVME_AUTH + &dev_attr_dhchap_secret.attr, + &dev_attr_dhchap_ctrl_secret.attr, +#endif
Not sure if we need to change the user interface according to kernel CONFIGs
Quoted 108 lines
drivers/nvme/host/core.c +11
-1NULL };@@ -3538,6 +3661,10 @@ static umode_t nvme_dev_attrs_are_visible(struct kobject *kobj,return 0 ;if (a == &dev_attr_fast_io_fail_tmo.attr && !ctrl->opts)return 0 ; +#ifdef CONFIG_NVME_AUTH +if (a == &dev_attr_dhchap_secret.attr && !ctrl->opts) +return 0 ; +#endif return a->mode; }@@ -4302,8 +4429,10 @@ static void nvme_handle_aen_notice(struct nvme_ctrl *ctrl, u32 result)* recovery actions from interfering with the controller's * firmware activation. */ -if (nvme_change_ctrl_state (ctrl,NVME_CTRL_RESETTING )) +if (nvme_change_ctrl_state (ctrl,NVME_CTRL_RESETTING )) { +nvme_auth_stop (ctrl);queue_work (nvme_wq, &ctrl->fw_act_work); + }break ;#ifdef CONFIG_NVME_MULTIPATH case NVME_AER_NOTICE_ANA :@@ -4350,6 +4479,7 @@ EXPORT_SYMBOL_GPL(nvme_complete_async_event);void nvme_stop_ctrl (struct nvme_ctrl *ctrl) {nvme_mpath_stop (ctrl); +nvme_auth_stop (ctrl);nvme_stop_keep_alive (ctrl);nvme_stop_failfast_work (ctrl);flush_work (&ctrl->async_event_work);@@ -4404,6 +4534,8 @@ static void nvme_free_ctrl(struct device *dev)nvme_free_cels (ctrl);nvme_mpath_uninit (ctrl); +nvme_auth_stop (ctrl); +nvme_auth_free (ctrl);__free_page (ctrl->discard_page);if (subsys) {@@ -4494,6 +4626,7 @@ int nvme_init_ctrl(struct nvme_ctrl *ctrl, struct device *dev,nvme_fault_inject_init (&ctrl->fault_inject,dev_name (ctrl->device));nvme_mpath_init_ctrl (ctrl); +nvme_auth_init_ctrl (ctrl);return 0 ; out_free_name:drivers/nvme/host/fabrics.c +26
-2@@ -370,6 +370,7 @@ int nvmf_connect_admin_queue(struct nvme_ctrl *ctrl)union nvme_result res;struct nvmf_connect_data *data;int ret; +u32 result; cmd.connect.opcode = nvme_fabrics_command; cmd.connect.fctype = nvme_fabrics_type_connect;@@ -402,8 +403,25 @@ int nvmf_connect_admin_queue(struct nvme_ctrl *ctrl) goto out_free_data; } - ctrl->cntlid =le16_to_cpu (res.u16); - + result =le32_to_cpu (res.u32); + ctrl->cntlid = result &0xFFFF ; +if ((result >>16 ) &2 ) { +/* Authentication required */ + ret =nvme_auth_negotiate (ctrl,NVME_QID_ANY ); +if (ret) { +dev_warn (ctrl->device, +"qid 0: authentication setup failed\n" ); + ret =NVME_SC_AUTH_REQUIRED ; + goto out_free_data; + } + ret =nvme_auth_wait (ctrl,NVME_QID_ANY ); +if (ret) +dev_warn (ctrl->device, +"qid 0: authentication failed\n" ); +else +dev_info (ctrl->device, +"qid 0: authenticated\n" ); + } out_free_data:kfree (data);return ret;@@ -436,6 +454,7 @@ int nvmf_connect_io_queue(struct nvme_ctrl *ctrl, u16 qid)struct nvmf_connect_data *data;union nvme_result res;int ret; +u32 result; cmd.connect.opcode = nvme_fabrics_command; cmd.connect.fctype = nvme_fabrics_type_connect;@@ -461,6 +480,21 @@ int nvmf_connect_io_queue(struct nvme_ctrl *ctrl, u16 qid)nvmf_log_connect_error (ctrl, ret,le32_to_cpu (res.u32), &cmd, data); } + result =le32_to_cpu (res.u32); +if ((result >>16 ) &2 ) { +/* Authentication required */ + ret =nvme_auth_negotiate (ctrl, qid); +if (ret) {
drivers/nvme/host/fabrics.c int nvmf_connect_io_queue(struct nvme_ctrl *ctrl, u16 qid) · line 497
Quoted 10 lines
drivers/nvme/host/fabrics.c +10
-0+dev_warn (ctrl->device, +"qid %d: authentication setup failed\n" , qid); + ret =NVME_SC_AUTH_REQUIRED ; + }else { + ret =nvme_auth_wait (ctrl, qid); +if (ret) +dev_warn (ctrl->device, +"qid %u: authentication failed\n" , qid); + } + }
can we add helper function to the above code to avoid duplication ?
Quoted 190 lines
drivers/nvme/host/fabrics.c +40
-1kfree (data);return ret; }@@ -553,6 +587,8 @@ static const match_table_t opt_tokens = { { NVMF_OPT_TOS, "tos=%d" }, { NVMF_OPT_FAIL_FAST_TMO, "fast_io_fail_tmo=%d" }, { NVMF_OPT_DISCOVERY, "discovery" }, + { NVMF_OPT_DHCHAP_SECRET, "dhchap_secret=%s" }, + { NVMF_OPT_DHCHAP_CTRL_SECRET, "dhchap_ctrl_secret=%s" }, { NVMF_OPT_ERR, NULL } };@@ -831,6 +867,34 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts,case NVMF_OPT_DISCOVERY : opts->discovery_nqn = true;break ; +case NVMF_OPT_DHCHAP_SECRET : + p =match_strdup (args); +if (!p) { + ret = -ENOMEM ; + goto out; + } +if (strlen (p) <11 ||strncmp (p,"DHHC-1:" ,7 )) { +pr_err ("Invalid DH-CHAP secret %s\n" , p); + ret = -EINVAL ; + goto out; + } +kfree (opts->dhchap_secret); + opts->dhchap_secret = p; +break ; +case NVMF_OPT_DHCHAP_CTRL_SECRET : + p =match_strdup (args); +if (!p) { + ret = -ENOMEM ; + goto out; + } +if (strlen (p) <11 ||strncmp (p,"DHHC-1:" ,7 )) { +pr_err ("Invalid DH-CHAP secret %s\n" , p); + ret = -EINVAL ; + goto out; + } +kfree (opts->dhchap_ctrl_secret); + opts->dhchap_ctrl_secret = p; +break ;default :pr_warn ("unknown parameter or missing value '%s' in ctrl creation request\n" , p);@@ -949,6 +1013,7 @@ void nvmf_free_options(struct nvmf_ctrl_options *opts)kfree (opts->subsysnqn);kfree (opts->host_traddr);kfree (opts->host_iface); +kfree (opts->dhchap_secret);kfree (opts); }EXPORT_SYMBOL_GPL (nvmf_free_options);@@ -958,7 +1023,8 @@ EXPORT_SYMBOL_GPL(nvmf_free_options); NVMF_OPT_KATO | NVMF_OPT_HOSTNQN | \ NVMF_OPT_HOST_ID | NVMF_OPT_DUP_CONNECT |\ NVMF_OPT_DISABLE_SQFLOW | NVMF_OPT_DISCOVERY |\ - NVMF_OPT_FAIL_FAST_TMO) + NVMF_OPT_FAIL_FAST_TMO | NVMF_OPT_DHCHAP_SECRET |\ + NVMF_OPT_DHCHAP_CTRL_SECRET)static struct nvme_ctrl *nvmf_create_ctrl (struct device *dev,const char *buf)@@ -1175,7 +1241,14 @@ static void __exit nvmf_exit(void)BUILD_BUG_ON (sizeof (struct nvmf_connect_command ) !=64 );BUILD_BUG_ON (sizeof (struct nvmf_property_get_command ) !=64 );BUILD_BUG_ON (sizeof (struct nvmf_property_set_command ) !=64 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_send_command ) !=64 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_receive_command ) !=64 );BUILD_BUG_ON (sizeof (struct nvmf_connect_data ) !=1024 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_dhchap_negotiate_data ) !=8 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_dhchap_challenge_data ) !=16 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_dhchap_reply_data ) !=16 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_dhchap_success1_data ) !=16 ); +BUILD_BUG_ON (sizeof (struct nvmf_auth_dhchap_success2_data ) !=16 ); }MODULE_LICENSE ("GPL v2" );drivers/nvme/host/fabrics.h +7
-0@@ -68,6 +68,8 @@ enum {NVMF_OPT_FAIL_FAST_TMO =1 <<20 ,NVMF_OPT_HOST_IFACE =1 <<21 ,NVMF_OPT_DISCOVERY =1 <<22 , +NVMF_OPT_DHCHAP_SECRET =1 <<23 , + NVMF_OPT_DHCHAP_CTRL_SECRET = 1 << 24, };/** @@ -97,6 +99,9 @@ enum {* @max_reconnects: maximum number of allowed reconnect attempts before removing * the controller, (-1) means reconnect forever, zero means remove * immediately; +* @dhchap_secret: DH-HMAC-CHAP secret +* @dhchap_ctrl_secret: DH-HMAC-CHAP controller secret for bi-directional +* authentication * @disable_sqflow: disable controller sq flow control * @hdr_digest: generate/verify header digest (TCP) * @data_digest: generate/verify data digest (TCP) @@ -121,6 +126,8 @@ struct nvmf_ctrl_options {unsigned int kato;struct nvmf_host *host;int max_reconnects; +char *dhchap_secret; +char *dhchap_ctrl_secret;bool disable_sqflow;bool hdr_digest;bool data_digest;drivers/nvme/host/nvme.h +31
-0@@ -324,6 +324,15 @@ struct nvme_ctrl {struct work_struct ana_work;#endif +#ifdef CONFIG_NVME_AUTH +struct work_struct dhchap_auth_work; +struct list_head dhchap_auth_list; +struct mutex dhchap_auth_mutex; +struct nvme_dhchap_key *host_key; +struct nvme_dhchap_key *ctrl_key; +u16 transaction; +#endif +/* Power saving configuration */ u64 ps_max_latency_us;bool apst_enabled;@@ -910,6 +919,28 @@ static inline bool nvme_ctrl_sgl_supported(struct nvme_ctrl *ctrl)return ctrl->sgls & ((1 <<0 ) | (1 <<1 )); } +#ifdef CONFIG_NVME_AUTH +void nvme_auth_init_ctrl (struct nvme_ctrl *ctrl); +void nvme_auth_stop (struct nvme_ctrl *ctrl); +int nvme_auth_negotiate (struct nvme_ctrl *ctrl,int qid); +int nvme_auth_wait (struct nvme_ctrl *ctrl,int qid); +void nvme_auth_reset (struct nvme_ctrl *ctrl); +void nvme_auth_free (struct nvme_ctrl *ctrl); +int nvme_auth_generate_key (u8 *secret,struct nvme_dhchap_key **ret_key); +#else +static inline void nvme_auth_init_ctrl (struct nvme_ctrl *ctrl) {}; +static inline void nvme_auth_stop (struct nvme_ctrl *ctrl) {}; +static inline int nvme_auth_negotiate (struct nvme_ctrl *ctrl,int qid) +{ +return -EPROTONOSUPPORT ; +} +static inline int nvme_auth_wait (struct nvme_ctrl *ctrl,int qid) +{ +return NVME_SC_AUTH_REQUIRED ; +} +static inline void nvme_auth_free (struct nvme_ctrl *ctrl) {}; +#endif +u32 nvme_command_effects (struct nvme_ctrl *ctrl,struct nvme_ns *ns,u8 opcode);int nvme_execute_passthru_rq (struct request *rq);drivers/nvme/host/rdma.c +1
-0@@ -1199,6 +1199,7 @@ static void nvme_rdma_error_recovery_work(struct work_struct *work)struct nvme_rdma_ctrl *ctrl =container_of (work, struct nvme_rdma_ctrl, err_work); +nvme_auth_stop (&ctrl->ctrl);nvme_stop_keep_alive (&ctrl->ctrl);nvme_rdma_teardown_io_queues (ctrl, false);nvme_start_queues (&ctrl->ctrl);drivers/nvme/host/tcp.c +1
-0@@ -2096,6 +2096,7 @@ static void nvme_tcp_error_recovery_work(struct work_struct *work) struct nvme_tcp_ctrl, err_work);struct nvme_ctrl *ctrl = &tcp_ctrl->ctrl; +nvme_auth_stop (ctrl);nvme_stop_keep_alive (ctrl);nvme_tcp_teardown_io_queues (ctrl, false);/* unquiesce to fail fast pending requests */ drivers/nvme/host/trace.c +0
-0
drivers/nvme/host/trace.c static const char *nvme_trace_fabrics_property_get(struct trace_seq *p, u8 *spc) · line 288
Quoted 2 lines
drivers/nvme/host/trace.c +0
-0@@ -287,6 +287,34 @@ static const char *nvme_trace_fabrics_property_get(struct trace_seq *p, u8 *spc)return ret; }
I think we need to add a dedicated commit for the traces.
Quoted 33 lines
drivers/nvme/host/trace.c +28
-0+static const char *nvme_trace_fabrics_auth_send (struct trace_seq *p,u8 *spc) +{ +const char *ret =trace_seq_buffer_ptr (p); +u8 spsp0 = spc[1 ]; +u8 spsp1 = spc[2 ]; +u8 secp = spc[3 ]; +u32 tl =get_unaligned_le32 (spc +4 ); + +trace_seq_printf (p,"spsp0=%02x, spsp1=%02x, secp=%02x, tl=%u" , + spsp0, spsp1, secp, tl); +trace_seq_putc (p,0 ); +return ret; +} + +static const char *nvme_trace_fabrics_auth_receive (struct trace_seq *p,u8 *spc) +{ +const char *ret =trace_seq_buffer_ptr (p); +u8 spsp0 = spc[1 ]; +u8 spsp1 = spc[2 ]; +u8 secp = spc[3 ]; +u32 al =get_unaligned_le32 (spc +4 ); + +trace_seq_printf (p,"spsp0=%02x, spsp1=%02x, secp=%02x, al=%u" , + spsp0, spsp1, secp, al); +trace_seq_putc (p,0 ); +return ret; +} +static const char *nvme_trace_fabrics_common (struct trace_seq *p,u8 *spc) {const char *ret =trace_seq_buffer_ptr (p);
drivers/nvme/host/trace.c const char *nvme_trace_parse_fabrics_cmd(struct trace_seq *p, · line 343
Quoted 10 lines
drivers/nvme/host/trace.c +4
-0@@ -306,6 +334,10 @@ const char *nvme_trace_parse_fabrics_cmd(struct trace_seq *p,return nvme_trace_fabrics_connect (p, spc);case nvme_fabrics_type_property_get:return nvme_trace_fabrics_property_get (p, spc); +case nvme_fabrics_type_auth_send: +return nvme_trace_fabrics_auth_send (p, spc); +case nvme_fabrics_type_auth_receive: +return nvme_trace_fabrics_auth_receive (p, spc);default :return nvme_trace_fabrics_common (p, spc); }
did you test this code with NVMe/RDMA transport too ?
Hannes Reinecke
maintainerRe: [PATCH 07/12] nvme: Implement In-Band authentication
Quoted 12 lines · Max Gurtovoy
Hi Hannes,
Quoted 8 lines · Hannes Reinecke
Implement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds two new fabric options '
dhchap_secret' to specify the pre-shared key (in ASCII respresentation according to NVMe 2.0 section 8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specify the pre-shared controller key for bi-directional authentication of both the host and the controller.
Re-authentication can be triggered by writing the PSK into the new controller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.
Quoted 5 lines
Can you please add to commit log an example of the process ?
From target configuration through the 'nvme connect' cmd.
Please check:
https://github.com/hreinecke/blktests/tree/auth.v3
That contains the blktest scripts I'm using to validate the implementation.
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
Re: [PATCH 07/12] nvme: Implement In-Band authentication
Quoted 19 lines · Hannes Reinecke
Quoted 12 lines · Max Gurtovoy
Hi Hannes,
Quoted 8 lines · Hannes Reinecke
Implement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds two new fabric options '
dhchap_secret' to specify the pre-shared key (in ASCII respresentation according to NVMe 2.0 section 8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specify the pre-shared controller key for bi-directional authentication of both the host and the controller.
Re-authentication can be triggered by writing the PSK into the new controller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.Quoted 5 lines
Can you please add to commit log an example of the process ?
From target configuration through the 'nvme connect' cmd.
Quoted 7 lines
Please check:
That contains the blktest scripts I'm using to validate the implementation.
blktest is great but for features in this magnitude I think we need to add a simple usage example in the commit log or in the cover letter.
for someone that is not familiar with blktests, one should start reverse engineering 4000 LOC to use it.
Cheers,
Max.
Thanks for implementing this important feature.
Quoted 3 lines
Cheers,
Hannes
Hannes Reinecke
maintainerRe: [PATCH 07/12] nvme: Implement In-Band authentication
Quoted 23 lines · Max Gurtovoy
Quoted 21 lines · Hannes Reinecke
Quoted 12 lines · Max Gurtovoy
Hi Hannes,
Quoted 8 lines · Hannes Reinecke
Implement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds two new fabric options '
dhchap_secret' to specify the pre-shared key (in ASCII respresentation according to NVMe 2.0 section 8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specify the pre-shared controller key for bi-directional authentication of both the host and the controller.
Re-authentication can be triggered by writing the PSK into the new controller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.Quoted 5 lines
Can you please add to commit log an example of the process ?
From target configuration through the 'nvme connect' cmd.
Please check:
Quoted 9 lines
Quoted 5 lines
That contains the blktest scripts I'm using to validate the implementation.
blktest is great but for features in this magnitude I think we need to add a simple usage example in the commit log or in the cover letter.
for someone that is not familiar with blktests, one should start reverse engineering 4000 LOC to use it.
Right.
Essentially it boils down to this:
nvme gen-dhchap-key > host_key.txt
nvme gen-dhchap-key > target_key.txt
mkdir /sys/kernel/config/nvmet/hosts/<hostnqn>
cd /sys/kernel/config/nvmet/hosts/<hostnqn>
cat host_key.txt > dhchap_key
cat target_key.txt > dhchap_ctrl_key
<link 'hostnqn' to the target subsystem>
And then one the host you need to call
'nvme connect ... --dhchap-key=$(cat host_key)'
And things should work.
But I can put a more detailed description in the commit log.
Note, I'm waiting for Herbert Xu to merge his 'cryptodev' tree with upstream; once that's done I'll be submitting these patches.
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
Hannes Reinecke
maintainerPATCH v8 8/12 nvme-auth: Diffie-Hellman key exchange support
In reply to Hannes ReineckeImplement Diffie-Hellman key exchange using FFDHE groups for NVMe In-Band Authentication.
--- drivers/nvme/host/Kconfig | 1 + drivers/nvme/host/auth.c | 412 +++++++++++++++++++++++++++++++++++++- drivers/nvme/host/auth.h | 8 + 3 files changed, 415 insertions(+), 6 deletions(-)
drivers/nvme/host/Kconfig +1 -0
@@ -90,6 +90,7 @@ config NVME_AUTH select CRYPTO_HMAC select CRYPTO_SHA256 select CRYPTO_SHA512 + select CRYPTO_FFDHE help This provides support for NVMe over Fabrics In-Band Authentication.
drivers/nvme/host/auth.c +406 -6
504 lines not on this page · raw message
drivers/nvme/host/auth.h +8 -0
@@ -30,5 +30,13 @@ struct nvme_dhchap_key *nvme_auth_extract_key(unsigned char *secret, u8 key_hash);void nvme_auth_free_key (struct nvme_dhchap_key *key);u8 *nvme_auth_transform_key (struct nvme_dhchap_key *key,char *nqn); +int nvme_auth_augmented_challenge (u8 hmac_id,u8 *skey,size_t skey_len, +u8 *challenge,u8 *aug,size_t hlen); +int nvme_auth_gen_privkey (struct crypto_kpp *dh_tfm,u8 dh_gid); +int nvme_auth_gen_pubkey (struct crypto_kpp *dh_tfm, +u8 *host_key,size_t host_key_len); +int nvme_auth_gen_shared_secret (struct crypto_kpp *dh_tfm, +u8 *ctrl_key,size_t ctrl_key_len, +u8 *sess_key,size_t sess_key_len);#endif /* _NVME_AUTH_H */
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 9/12 nvmet: parse fabrics commands on io queues
In reply to Hannes ReineckeSome fabrics commands can be sent via io queues, so add a new function nvmet_parse_fabrics_io_cmd() and rename the existing nvmet_parse_fabrics_cmd() to nvmet_parse_fabrics_admin_cmd().
--- drivers/nvme/target/core.c | 4 ++++ drivers/nvme/target/fabrics-cmd.c | 17 ++++++++++++++++- drivers/nvme/target/nvmet.h | 3 ++- 3 files changed, 22 insertions(+), 2 deletions(-)
drivers/nvme/target/core.c +4 -0
@@ -863,8 +863,12 @@ static inline u16 nvmet_io_cmd_check_access(struct nvmet_req *req)static u16 nvmet_parse_io_cmd (struct nvmet_req *req) { +struct nvme_command *cmd = req->cmd;u16 ret; +if (nvme_is_fabrics (cmd)) +return nvmet_parse_fabrics_io_cmd (req); + ret =nvmet_check_ctrl_status (req);if (unlikely (ret))return ret;
drivers/nvme/target/fabrics-cmd.c +16 -1
@@ -82,7 +82,7 @@ static void nvmet_execute_prop_get(struct nvmet_req *req)nvmet_req_complete (req, status); } -u16 nvmet_parse_fabrics_cmd (struct nvmet_req *req) +u16 nvmet_parse_fabrics_admin_cmd (struct nvmet_req *req) {struct nvme_command *cmd = req->cmd;
@@ -103,6 +103,21 @@ u16 nvmet_parse_fabrics_cmd(struct nvmet_req *req)return 0 ; } +u16 nvmet_parse_fabrics_io_cmd (struct nvmet_req *req) +{ +struct nvme_command *cmd = req->cmd; + +switch (cmd->fabrics.fctype) { +default : +pr_debug ("received unknown capsule type 0x%x\n" , + cmd->fabrics.fctype); + req->error_loc = offsetof(struct nvmf_common_command , fctype); +return NVME_SC_INVALID_OPCODE |NVME_SC_DNR ; + } + +return 0 ; +} +static u16 nvmet_install_queue (struct nvmet_ctrl *ctrl,struct nvmet_req *req) {struct nvmf_connect_command *c = &req->cmd->connect;
drivers/nvme/target/nvmet.h +2 -1
@@ -418,7 +418,8 @@ u16 nvmet_file_parse_io_cmd(struct nvmet_req *req);u16 nvmet_bdev_zns_parse_io_cmd (struct nvmet_req *req);u16 nvmet_parse_admin_cmd (struct nvmet_req *req);u16 nvmet_parse_discovery_cmd (struct nvmet_req *req); -u16 nvmet_parse_fabrics_cmd (struct nvmet_req *req); +u16 nvmet_parse_fabrics_admin_cmd (struct nvmet_req *req); +u16 nvmet_parse_fabrics_io_cmd (struct nvmet_req *req);bool nvmet_req_init (struct nvmet_req *req,struct nvmet_cq *cq,struct nvmet_sq *sq,const struct nvmet_fabrics_ops *ops);
Signature · 1 line
2.29.2
Re: [PATCH 09/12] nvmet: parse fabrics commands on io queues
Hannes Reinecke
maintainerPATCH v8 10/12 nvmet: Implement basic In-Band Authentication
In reply to Hannes ReineckeImplement NVMe-oF In-Band authentication according to NVMe TPAR 8006. This patch adds three additional configfs entries 'dhchap_key', 'dhchap_ctrl_key', and 'dhchap_hash' to the 'host' configfs directory. The 'dhchap_key' and 'dhchap_ctrl_key' entries need to be in the ASCII format as specified in NVMe Base Specification v2.0 section 8.13.5.8 'Secret representation'.
'dhchap_hash' defaults to 'hmac(sha256)', and can be written to to switch to a different HMAC algorithm.
--- drivers/nvme/target/Kconfig | 12 + drivers/nvme/target/Makefile | 1 + drivers/nvme/target/admin-cmd.c | 6 +- drivers/nvme/target/auth.c | 367 ++++++++++++++++++ drivers/nvme/target/configfs.c | 107 +++++- drivers/nvme/target/core.c | 11 + drivers/nvme/target/fabrics-cmd-auth.c | 491 +++++++++++++++++++++++++ drivers/nvme/target/fabrics-cmd.c | 38 +- drivers/nvme/target/nvmet.h | 62 ++++ 9 files changed, 1091 insertions(+), 4 deletions(-) create mode 100644 drivers/nvme/target/auth.c create mode 100644 drivers/nvme/target/fabrics-cmd-auth.c
drivers/nvme/target/Kconfig +12 -0
@@ -83,3 +83,15 @@ config NVME_TARGET_TCP devices over TCP. If unsure, say N. + +config NVME_TARGET_AUTH + bool "NVMe over Fabrics In-band Authentication support" + depends on NVME_TARGET + depends on NVME_AUTH + select CRYPTO_HMAC + select CRYPTO_SHA256 + select CRYPTO_SHA512 + help + This enables support for NVMe over Fabrics In-band Authentication + + If unsure, say N.
drivers/nvme/target/Makefile +1 -0
@@ -13,6 +13,7 @@ nvmet-y += core.o configfs.o admin-cmd.o fabrics-cmd.o \ discovery.o io-cmd-file.o io-cmd-bdev.o nvmet-$(CONFIG_NVME_TARGET_PASSTHRU) += passthru.o nvmet-$(CONFIG_BLK_DEV_ZONED) += zns.o +nvmet-$(CONFIG_NVME_TARGET_AUTH) += fabrics-cmd-auth.o auth.o nvme-loop-y += loop.o nvmet-rdma-y += rdma.o nvmet-fc-y += fc.o
drivers/nvme/target/admin-cmd.c +5 -1
@@ -1013,7 +1013,11 @@ u16 nvmet_parse_admin_cmd(struct nvmet_req *req)u16 ret;if (nvme_is_fabrics (cmd)) -return nvmet_parse_fabrics_cmd (req); +return nvmet_parse_fabrics_admin_cmd (req); + +if (unlikely (!nvmet_check_auth_status (req))) +return NVME_SC_AUTH_REQUIRED |NVME_SC_DNR ; +if (nvmet_is_disc_subsys (nvmet_req_subsys (req)))return nvmet_parse_discovery_cmd (req);
drivers/nvme/target/auth.c new file +367 -0
367 lines not on this page · raw message
drivers/nvme/target/configfs.c +106 -1
136 lines not on this page · raw message
drivers/nvme/target/core.c +11 -0
@@ -793,6 +793,7 @@ void nvmet_sq_destroy(struct nvmet_sq *sq)wait_for_completion (&sq->confirm_done);wait_for_completion (&sq->free_done);percpu_ref_exit (&sq->ref); +nvmet_auth_sq_free (sq);if (ctrl) {/*
@@ -869,6 +870,9 @@ static u16 nvmet_parse_io_cmd(struct nvmet_req *req)if (nvme_is_fabrics (cmd))return nvmet_parse_fabrics_io_cmd (req); +if (unlikely (!nvmet_check_auth_status (req))) +return NVME_SC_AUTH_REQUIRED |NVME_SC_DNR ; + ret =nvmet_check_ctrl_status (req);if (unlikely (ret))return ret;
@@ -1273,6 +1277,11 @@ u16 nvmet_check_ctrl_status(struct nvmet_req *req) req->cmd->common.opcode, req->sq->qid);return NVME_SC_CMD_SEQ_ERROR |NVME_SC_DNR ; } + +if (unlikely (!nvmet_check_auth_status (req))) { +pr_warn ("qid %d not authenticated\n" , req->sq->qid); +return NVME_SC_AUTH_REQUIRED |NVME_SC_DNR ; + }return 0 ; }
@@ -1463,6 +1472,8 @@ static void nvmet_ctrl_free(struct kref *ref)flush_work (&ctrl->async_event_work);cancel_work_sync (&ctrl->fatal_err_work); +nvmet_destroy_auth (ctrl); +ida_simple_remove (&cntlid_ida, ctrl->cntlid);nvmet_async_events_free (ctrl);
drivers/nvme/target/fabrics-cmd-auth.c new file +491 -0
491 lines not on this page · raw message
drivers/nvme/target/fabrics-cmd.c +36 -2
@@ -93,6 +93,14 @@ u16 nvmet_parse_fabrics_admin_cmd(struct nvmet_req *req)case nvme_fabrics_type_property_get: req->execute = nvmet_execute_prop_get;break ; +#ifdef CONFIG_NVME_TARGET_AUTH +case nvme_fabrics_type_auth_send: + req->execute = nvmet_execute_auth_send; +break ; +case nvme_fabrics_type_auth_receive: + req->execute = nvmet_execute_auth_receive; +break ; +#endif default :pr_debug ("received unknown capsule type 0x%x\n" , cmd->fabrics.fctype);
@@ -108,6 +116,14 @@ u16 nvmet_parse_fabrics_io_cmd(struct nvmet_req *req)struct nvme_command *cmd = req->cmd;switch (cmd->fabrics.fctype) { +#ifdef CONFIG_NVME_TARGET_AUTH +case nvme_fabrics_type_auth_send: + req->execute = nvmet_execute_auth_send; +break ; +case nvme_fabrics_type_auth_receive: + req->execute = nvmet_execute_auth_receive; +break ; +#endif default :pr_debug ("received unknown capsule type 0x%x\n" , cmd->fabrics.fctype);
@@ -188,6 +204,7 @@ static void nvmet_execute_admin_connect(struct nvmet_req *req)struct nvmf_connect_data *d;struct nvmet_ctrl *ctrl =NULL ;u16 status =0 ; +int ret;if (!nvmet_check_transfer_len (req,sizeof (struct nvmf_connect_data )))return ;
@@ -230,18 +247,32 @@ static void nvmet_execute_admin_connect(struct nvmet_req *req)uuid_copy (&ctrl->hostid, &d->hostid); + ret =nvmet_setup_auth (ctrl); +if (ret <0 ) { +pr_err ("Failed to setup authentication, error %d\n" , ret); +nvmet_ctrl_put (ctrl); +if (ret == -EPERM ) + status = (NVME_SC_CONNECT_INVALID_HOST |NVME_SC_DNR ); +else + status =NVME_SC_INTERNAL ; + goto out; + } + status =nvmet_install_queue (ctrl, req);if (status) {nvmet_ctrl_put (ctrl); goto out; } -pr_info ("creating %s controller %d for subsystem %s for NQN %s%s.\n" , +pr_info ("creating %s controller %d for subsystem %s for NQN %s%s%s.\n" ,nvmet_is_disc_subsys (ctrl->subsys) ?"discovery" :"nvm" , ctrl->cntlid, ctrl->subsys->subsysnqn, ctrl->hostnqn, - ctrl->pi_support ?" T10-PI is enabled" :"" ); + ctrl->pi_support ?" T10-PI is enabled" :"" , +nvmet_has_auth (ctrl) ?" with DH-HMAC-CHAP" :"" ); req->cqe->result.u16 =cpu_to_le16 (ctrl->cntlid); +if (nvmet_has_auth (ctrl)) +nvmet_init_auth (ctrl, req); out:kfree (d); complete:
@@ -301,6 +332,9 @@ static void nvmet_execute_io_connect(struct nvmet_req *req) req->cqe->result.u16 =cpu_to_le16 (ctrl->cntlid);pr_debug ("adding queue %d to ctrl %d.\n" , qid, ctrl->cntlid); + req->cqe->result.u16 =cpu_to_le16 (ctrl->cntlid); +if (nvmet_has_auth (ctrl)) +nvmet_init_auth (ctrl, req); out:kfree (d);
drivers/nvme/target/nvmet.h +62 -0
84 lines not on this page · raw message
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 11/12 nvmet-auth: Diffie-Hellman key exchange support
In reply to Hannes ReineckeImplement Diffie-Hellman key exchange using FFDHE groups for NVMe In-Band Authentication.
This patch adds a new host configfs attribute 'dhchap_dhgroup' to select the FFDHE group to use.
--- drivers/nvme/target/Kconfig | 1 + drivers/nvme/target/auth.c | 155 +++++++++++++++++++++++++ drivers/nvme/target/configfs.c | 31 +++++ drivers/nvme/target/fabrics-cmd-auth.c | 41 +++++-- drivers/nvme/target/nvmet.h | 9 ++ 5 files changed, 229 insertions(+), 8 deletions(-)
drivers/nvme/target/Kconfig +1 -0
@@ -91,6 +91,7 @@ config NVME_TARGET_AUTH select CRYPTO_HMAC select CRYPTO_SHA256 select CRYPTO_SHA512 + select CRYPTO_FFDHE help This enables support for NVMe over Fabrics In-band Authentication
drivers/nvme/target/auth.c +155 -0
188 lines not on this page · raw message
drivers/nvme/target/configfs.c +31 -0
@@ -1784,10 +1784,41 @@ static ssize_t nvmet_host_dhchap_hash_store(struct config_item *item,CONFIGFS_ATTR (nvmet_host_, dhchap_hash); +static ssize_t nvmet_host_dhchap_dhgroup_show (struct config_item *item, +char *page) +{ +struct nvmet_host *host =to_host (item); +const char *dhgroup =nvme_auth_dhgroup_name (host->dhchap_dhgroup_id); + +return sprintf (page,"%s\n" , dhgroup ? dhgroup :"none" ); +} + +static ssize_t nvmet_host_dhchap_dhgroup_store (struct config_item *item, +const char *page,size_t count) +{ +struct nvmet_host *host =to_host (item); +int dhgroup_id; + + dhgroup_id =nvme_auth_dhgroup_id (page); +if (dhgroup_id ==NVME_AUTH_DHGROUP_INVALID ) +return -EINVAL ; +if (dhgroup_id !=NVME_AUTH_DHGROUP_NULL ) { +const char *kpp =nvme_auth_dhgroup_kpp (dhgroup_id); + +if (!crypto_has_kpp (kpp,0 ,0 )) +return -EINVAL ; + } + host->dhchap_dhgroup_id = dhgroup_id; +return count; +} + +CONFIGFS_ATTR (nvmet_host_, dhchap_dhgroup); +static struct configfs_attribute *nvmet_host_attrs[] = { &nvmet_host_attr_dhchap_key, &nvmet_host_attr_dhchap_ctrl_key, &nvmet_host_attr_dhchap_hash, + &nvmet_host_attr_dhchap_dhgroup,NULL , };#endif /* CONFIG_NVME_TARGET_AUTH */
drivers/nvme/target/fabrics-cmd-auth.c +33 -8
84 lines not on this page · raw message
drivers/nvme/target/nvmet.h +9 -0
@@ -225,6 +225,10 @@ struct nvmet_ctrl {struct nvme_dhchap_key *host_key;struct nvme_dhchap_key *ctrl_key;u8 shash_id; +struct crypto_kpp *dh_tfm; +u8 dh_gid; +u8 *dh_key; +size_t dh_keysize;#endif };
@@ -700,6 +704,7 @@ int nvmet_setup_auth(struct nvmet_ctrl *ctrl);void nvmet_init_auth (struct nvmet_ctrl *ctrl,struct nvmet_req *req);void nvmet_destroy_auth (struct nvmet_ctrl *ctrl);void nvmet_auth_sq_free (struct nvmet_sq *sq); +int nvmet_setup_dhgroup (struct nvmet_ctrl *ctrl,u8 dhgroup_id);bool nvmet_check_auth_status (struct nvmet_req *req);int nvmet_auth_host_hash (struct nvmet_req *req,u8 *response,unsigned int hash_len);
@@ -709,6 +714,10 @@ static inline bool nvmet_has_auth(struct nvmet_ctrl *ctrl) {return ctrl->host_key !=NULL ; } +int nvmet_auth_ctrl_exponential (struct nvmet_req *req, +u8 *buf,int buf_size); +int nvmet_auth_ctrl_sesskey (struct nvmet_req *req, +u8 *buf,int buf_size);#else static inline int nvmet_setup_auth (struct nvmet_ctrl *ctrl) {
Signature · 1 line
2.29.2
Hannes Reinecke
maintainerPATCH v8 12/12 nvmet-auth: expire authentication sessions
In reply to Hannes ReineckeEach authentication step is required to be completed within the KATO interval (or two minutes if not set). So add a workqueue function to reset the transaction ID and the expected next protocol step; this will automatically the next authentication command referring to the terminated authentication.
--- drivers/nvme/target/auth.c | 1 + drivers/nvme/target/fabrics-cmd-auth.c | 20 +++++++++++++++++++- drivers/nvme/target/nvmet.h | 1 + 3 files changed, 21 insertions(+), 1 deletion(-)
drivers/nvme/target/auth.c +1 -0
@@ -215,6 +215,7 @@ int nvmet_setup_auth(struct nvmet_ctrl *ctrl)void nvmet_auth_sq_free (struct nvmet_sq *sq) { +cancel_delayed_work (&sq->auth_expired_work);kfree (sq->dhchap_c1); sq->dhchap_c1 =NULL ;kfree (sq->dhchap_c2);
drivers/nvme/target/fabrics-cmd-auth.c +19 -1
@@ -12,9 +12,22 @@#include "nvmet.h" #include "../host/auth.h" +static void nvmet_auth_expired_work (struct work_struct *work) +{ +struct nvmet_sq *sq =container_of (to_delayed_work (work), + struct nvmet_sq, auth_expired_work); + +pr_debug ("%s: ctrl %d qid %d transaction %u expired, resetting\n" , + __func__, sq->ctrl->cntlid, sq->qid, sq->dhchap_tid); + sq->dhchap_step =NVME_AUTH_DHCHAP_MESSAGE_NEGOTIATE ; + sq->dhchap_tid =-1 ; +} +void nvmet_init_auth (struct nvmet_ctrl *ctrl,struct nvmet_req *req) {/* Initialize in-band authentication */ +INIT_DELAYED_WORK (&req->sq->auth_expired_work, + nvmet_auth_expired_work); req->sq->authenticated = false; req->sq->dhchap_step =NVME_AUTH_DHCHAP_MESSAGE_NEGOTIATE ; req->cqe->result.u32 |=0x2 <<16 ;
@@ -326,8 +339,13 @@ void nvmet_execute_auth_send(struct nvmet_req *req) req->cqe->result.u64 =0 ;nvmet_req_complete (req, status);if (req->sq->dhchap_step !=NVME_AUTH_DHCHAP_MESSAGE_SUCCESS2 && - req->sq->dhchap_step !=NVME_AUTH_DHCHAP_MESSAGE_FAILURE2 ) + req->sq->dhchap_step !=NVME_AUTH_DHCHAP_MESSAGE_FAILURE2 ) { +unsigned long auth_expire_secs = ctrl->kato ? ctrl->kato :120 ; + +mod_delayed_work (system_wq, &req->sq->auth_expired_work, + auth_expire_secs *HZ );return ; + }/* Final states, clear up variables */ nvmet_auth_sq_free (req->sq);if (req->sq->dhchap_step ==NVME_AUTH_DHCHAP_MESSAGE_FAILURE2 )
drivers/nvme/target/nvmet.h +1 -0
@@ -109,6 +109,7 @@ struct nvmet_sq {u32 sqhd;bool sqhd_disabled;#ifdef CONFIG_NVME_TARGET_AUTH +struct delayed_work auth_expired_work;bool authenticated;u16 dhchap_tid;u16 dhchap_status;
Signature · 1 line
2.29.2
Christoph Hellwig
maintainerSo if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
Hannes Reinecke
maintainerQuoted 6 lines · Christoph Hellwig
So if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
That is _actually_ being addressed already.
Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and FIPS-related thingies for the in-kernel DH crypto implementation (https://lore.kernel.org/linux-crypto/[email protected]/).
This obsoletes my preliminary patches, and I have ported my patchset to run on top of those.
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Sagi Grimberg
maintainerQuoted 7 lines
Quoted 7 lines
So if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
Quoted 6 lines
That is _actually_ being addressed already.
Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and FIPS-related thingies for the in-kernel DH crypto implementation (https://lore.kernel.org/linux-crypto/[email protected]/).This obsoletes my preliminary patches, and I have ported my patchset to run on top of those.
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
Hannes Reinecke
maintainerQuoted 15 lines · Sagi Grimberg
Quoted 15 lines
Quoted 7 lines
So if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
That is _actually_ being addressed already.
Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and FIPS-related thingies for the in-kernel DH crypto implementation
(https://lore.kernel.org/linux-crypto/[email protected]/).This obsoletes my preliminary patches, and I have ported my patchset to run on top of those.
Quoted 7 lines
Quoted 4 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
Sagi Grimberg
maintainerQuoted 23 lines
Quoted 15 lines
Quoted 15 lines
Quoted 7 lines
So if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
That is _actually_ being addressed already.
Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and FIPS-related thingies for the in-kernel DH crypto implementation
(https://lore.kernel.org/linux-crypto/[email protected]/).This obsoletes my preliminary patches, and I have ported my patchset to run on top of those.
Quoted 7 lines
Quoted 4 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
Quoted 6 lines
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Can we get a sense from the crypto folks to the state of Nicolais patchset?
Hannes Reinecke
maintainerQuoted 28 lines · Sagi Grimberg
Quoted 28 lines
Quoted 16 lines
Quoted 16 lines
Quoted 7 lines
So if we want to make progress on this we need the first 3 patches rewviewed by the crypto maintainers. In fact I'd prefer to get them merged through the crypto tree as well, and would make sure we have a branch that pulls them in for the nvme changes. I'll try to find some time to review the nvme bits as well.
That is _actually_ being addressed already.
Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and FIPS-related thingies for the in-kernel DH crypto implementation
(https://lore.kernel.org/linux-crypto/[email protected]/).This obsoletes my preliminary patches, and I have ported my patchset to run on top of those.
Quoted 7 lines
Quoted 4 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
Quoted 5 lines
Quoted 2 lines
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Can we get a sense from the crypto folks to the state of Nicolais patchset?
According to Nicolai things look good, rules seem to be that it'll be accepted if it has positive reviews (which it has) and no-one objected (which no-one did).
Other than that one would have to ask the maintainer. Herbert?
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
Sagi Grimberg
maintainerQuoted 16 lines
Quoted 16 lines
Quoted 15 lines
Quoted 8 lines
Quoted 5 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Quoted 8 lines
Quoted 2 lines
Can we get a sense from the crypto folks to the state of Nicolais patchset?
According to Nicolai things look good, rules seem to be that it'll be accepted if it has positive reviews (which it has) and no-one objected (which no-one did).
Other than that one would have to ask the maintainer. Herbert?
Any updates on this?
Hannes Reinecke
maintainerQuoted 19 lines · Sagi Grimberg
Quoted 19 lines
Quoted 18 lines
Quoted 9 lines
Quoted 8 lines
Quoted 5 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
Quoted 6 lines
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Can we get a sense from the crypto folks to the state of Nicolais patchset?
Quoted 7 lines
Quoted 5 lines
According to Nicolai things look good, rules seem to be that it'll be accepted if it has positive reviews (which it has) and no-one objected (which no-one did).
Other than that one would have to ask the maintainer. Herbert?Any updates on this?
Sigh.
Herbert suggested reworking the patch, and make ffdhe a separate algorithm (instead of having enums to specify the values for the existing DH algorithm). Discussion is ongoing :-(
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Sagi Grimberg
maintainerQuoted 25 lines
Quoted 25 lines
Quoted 24 lines
Quoted 13 lines
Quoted 13 lines
Quoted 8 lines
Quoted 5 lines
Question is how to continue from here; I can easily rebase my patchset and send it relative to Nicolais patches. But then we'll be bound to the acceptance of those patches, so I'm not quite sure if that's the best way to proceed.
Don't know if we have a choice here... What is the alternative you are proposing?
That's the thing, I don't really have a good alternative, either. It's just that I have so no idea about the crypto subsystem, and consequently wouldn't know how long we need to wait...
Quoted 5 lines
Quoted 2 lines
But yeah, Nicolais patchset is far superior to my attempts, so I'd be happy to ditch my preliminary attempts there.
Can we get a sense from the crypto folks to the state of Nicolais patchset?
According to Nicolai things look good, rules seem to be that it'll be accepted if it has positive reviews (which it has) and no-one objected (which no-one did).
Other than that one would have to ask the maintainer. Herbert?
Quoted 6 lines
Quoted 1 line
Any updates on this?
Sigh.
Herbert suggested reworking the patch, and make ffdhe a separate algorithm (instead of having enums to specify the values for the existing DH algorithm). Discussion is ongoing :-(
Hannes and co,
Do you know what is the state of this dependency? Or when should we expect to revisit this patch set?
Sagi Grimberg
maintainerQuoted 5 lines
Hannes and co,
Do you know what is the state of this dependency? Or when should we expect to revisit this patch set?
Ping?
Hannes Reinecke
maintainerQuoted 7 lines · Sagi Grimberg
Quoted 5 lines
Hannes and co,
Do you know what is the state of this dependency? Or when should we expect to revisit this patch set?
Ping?
Pondering what the next steps should be. Herbert Xu has merged Nicolais patchset, so I _could_ submit the patches, but then I would need to base it on Herberts cryptodev-2.6 branch. And without these patches my patchset won't compile.
So no sure how to proceed; sending the patches relative to Herberts tree? Waiting for the patches to appear upstream? Not sure what'll be best...
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Kernel Storage Architect [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Christoph Hellwig
maintainerQuoted 6 lines · Hannes Reinecke
Pondering what the next steps should be. Herbert Xu has merged Nicolais patchset, so I _could_ submit the patches, but then I would need to base it on Herberts cryptodev-2.6 branch.
And without these patches my patchset won't compile.
So no sure how to proceed; sending the patches relative to Herberts tree? Waiting for the patches to appear upstream? Not sure what'll be best...
We're at 5.17-rc8, so hopefully they will in mainline for 5.18-rc1 in a few weeks. Let's wait until then to avoid complex tree dependencies.