public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Mae Kasza <git@badat.dev>
Cc: <kent.overstreet@linux.dev>, <linux-bcachefs@vger.kernel.org>
Subject: Re: [PATCH] Extract bch_crypt_update_passphrase function
Date: Wed, 14 Aug 2024 10:21:55 +0800	[thread overview]
Message-ID: <f22fb349-0fa1-43bd-82ec-a9328ab2feff@huawei.com> (raw)
In-Reply-To: <20240813173734.260952-2-git@badat.dev>



On 2024/8/14 1:37, Mae Kasza wrote:
> This also fixes a bug where the set-passphrase
> command failed to derive the key for disks initially
> formatted with --encrypted and --no_passphrase, due to
> bch_sb_crypt_init not configuring the KDF params if
> the passphrase wasn't specified during formatting.
> 
> Signed-off-by: Mae Kasza <git@badat.dev>
> ---
>   c_src/cmd_key.c | 26 ++++++++++----------------
>   c_src/crypto.c  | 43 ++++++++++++++++++++++++++++++++-----------
>   c_src/crypto.h  |  3 +++
>   3 files changed, 45 insertions(+), 27 deletions(-)
> 
> diff --git a/c_src/cmd_key.c b/c_src/cmd_key.c
> index adb0ac8d..ac8a94a8 100644
> --- a/c_src/cmd_key.c
> +++ b/c_src/cmd_key.c
> @@ -104,24 +104,19 @@ int cmd_set_passphrase(int argc, char *argv[])
>   	if (IS_ERR(c))
>   		die("Error opening %s: %s", argv[1], bch2_err_str(PTR_ERR(c)));
>   
> -	struct bch_sb_field_crypt *crypt = bch2_sb_field_get(c->disk_sb.sb, crypt);
> +	struct bch_sb *sb = c->disk_sb.sb;
> +	struct bch_sb_field_crypt *crypt = bch2_sb_field_get(sb, crypt);
>   	if (!crypt)
>   		die("Filesystem does not have encryption enabled");
>   
> -	struct bch_encrypted_key new_key;
> -	new_key.magic = BCH_KEY_MAGIC;
> -
> -	int ret = bch2_decrypt_sb_key(c, crypt, &new_key.key);
> +	struct bch_key key;
> +	int ret = bch2_decrypt_sb_key(c, crypt, &key);
>   	if (ret)
>   		die("Error getting current key");
>   
>   	char *new_passphrase = read_passphrase_twice("Enter new passphrase: ");
> -	struct bch_key passphrase_key = derive_passphrase(crypt, new_passphrase);
>   
> -	if (bch2_chacha_encrypt_key(&passphrase_key, __bch2_sb_key_nonce(c->disk_sb.sb),
> -				    &new_key, sizeof(new_key)))
> -		die("error encrypting key");
> -	crypt->key = new_key;
> +	bch_crypt_update_passphrase(sb, crypt, &key, new_passphrase);
>   
>   	bch2_revoke_key(c->disk_sb.sb);
>   	bch2_write_super(c);
> @@ -142,18 +137,17 @@ int cmd_remove_passphrase(int argc, char *argv[])
>   	if (IS_ERR(c))
>   		die("Error opening %s: %s", argv[1], bch2_err_str(PTR_ERR(c)));
>   
> -	struct bch_sb_field_crypt *crypt = bch2_sb_field_get(c->disk_sb.sb, crypt);
> +	struct bch_sb *sb = c->disk_sb.sb;
> +	struct bch_sb_field_crypt *crypt = bch2_sb_field_get(sb, crypt);
>   	if (!crypt)
>   		die("Filesystem does not have encryption enabled");
>   
> -	struct bch_encrypted_key new_key;
> -	new_key.magic = BCH_KEY_MAGIC;
> -
> -	int ret = bch2_decrypt_sb_key(c, crypt, &new_key.key);
> +	struct bch_key key;
> +	int ret = bch2_decrypt_sb_key(c, crypt, &key);
>   	if (ret)
>   		die("Error getting current key");
>   
> -	crypt->key = new_key;
> +	bch_crypt_update_passphrase(sb, crypt, &key, NULL);
>   
>   	bch2_write_super(c);
>   	bch2_fs_stop(c);
> diff --git a/c_src/crypto.c b/c_src/crypto.c
> index 32671bd8..301dbebe 100644
> --- a/c_src/crypto.c
> +++ b/c_src/crypto.c
> @@ -176,26 +176,47 @@ void bch_sb_crypt_init(struct bch_sb *sb,
>   		       struct bch_sb_field_crypt *crypt,
>   		       const char *passphrase)
>   {
> +	struct bch_key key;
> +	get_random_bytes(&key, sizeof(key));
> +
>   	crypt->key.magic = BCH_KEY_MAGIC;
> -	get_random_bytes(&crypt->key.key, sizeof(crypt->key.key));
> +	crypt->key.key = key;
>   
> -	if (passphrase) {
> +	bch_crypt_update_passphrase(sb, crypt, &key, passphrase);
> +}
>   
> +void bch_crypt_update_passphrase(
> +			struct bch_sb *sb,
> +			struct bch_sb_field_crypt *crypt,
> +			struct bch_key *key,
> +			const char *new_passphrase)
> +{
> +
> +	struct bch_encrypted_key new_key;
> +	new_key.magic = BCH_KEY_MAGIC;
> +	new_key.key = *key;
> +
> +	if(!new_passphrase) {
> +		crypt->key = new_key;
May be the helper like this is needed. But we could assign the 
crypt->key outside, which seems more reasonable according to the helper 
name. Just in my humble opinion.

Thanks,
Hongbo

> +		return;
> +	}
> +
> +	// If crypt already has an encrypted key reuse it's encryption params
> +	if (!bch2_key_is_encrypted(&crypt->key)) {
>   		SET_BCH_CRYPT_KDF_TYPE(crypt, BCH_KDF_SCRYPT);
>   		SET_BCH_KDF_SCRYPT_N(crypt, ilog2(16384));
>   		SET_BCH_KDF_SCRYPT_R(crypt, ilog2(8));
>   		SET_BCH_KDF_SCRYPT_P(crypt, ilog2(16));
> +	}
>   
> -		struct bch_key passphrase_key = derive_passphrase(crypt, passphrase);
> -
> -		assert(!bch2_key_is_encrypted(&crypt->key));
> +	struct bch_key passphrase_key = derive_passphrase(crypt, new_passphrase);
>   
> -		if (bch2_chacha_encrypt_key(&passphrase_key, __bch2_sb_key_nonce(sb),
> -					   &crypt->key, sizeof(crypt->key)))
> -			die("error encrypting key");
> +	if (bch2_chacha_encrypt_key(&passphrase_key, __bch2_sb_key_nonce(sb),
> +				    &new_key, sizeof(new_key)))
> +		die("error encrypting key");
>   
> -		assert(bch2_key_is_encrypted(&crypt->key));
> +	memzero_explicit(&passphrase_key, sizeof(passphrase_key));
>   
> -		memzero_explicit(&passphrase_key, sizeof(passphrase_key));
> -	}
> +	crypt->key = new_key;
> +	assert(bch2_key_is_encrypted(&crypt->key));
>   }
> diff --git a/c_src/crypto.h b/c_src/crypto.h
> index baea6d86..cd3baac8 100644
> --- a/c_src/crypto.h
> +++ b/c_src/crypto.h
> @@ -19,4 +19,7 @@ void bch2_add_key(struct bch_sb *, const char *, const char *, const char *);
>   void bch_sb_crypt_init(struct bch_sb *sb, struct bch_sb_field_crypt *,
>   		       const char *);
>   
> +void bch_crypt_update_passphrase(struct bch_sb *sb, struct bch_sb_field_crypt *crypt,
> +			struct bch_key *key, const char *new_passphrase);
> +
>   #endif /* _CRYPTO_H */

  reply	other threads:[~2024-08-14  2:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 21:40 Mae Kasza
2024-08-11 21:40 ` [PATCH] cmd_set_passphrase: initialize KDF parameters Mae Kasza
2024-08-12  1:41   ` Kent Overstreet
2024-08-12  2:50     ` Hongbo Li
2024-08-13 13:16       ` Mae Kasza
2024-08-13 17:37         ` [PATCH] Extract bch_crypt_update_passphrase function Mae Kasza
2024-08-14  2:21           ` Hongbo Li [this message]
2024-08-14 12:29             ` Mae Kasza
2024-08-14  2:10         ` [PATCH] cmd_set_passphrase: initialize KDF parameters Hongbo Li
2024-08-14 12:25           ` Mae Kasza
2024-09-13 21:39             ` Mae Kasza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f22fb349-0fa1-43bd-82ec-a9328ab2feff@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=git@badat.dev \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox