public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup-qemu 1/2] encryption key tracking: use fingerprint
Date: Tue, 24 Nov 2020 16:44:20 +0100	[thread overview]
Message-ID: <1606232547.d9bn5hfnnr.astroid@nora.none> (raw)
In-Reply-To: <1970589785.367.1606232217036@webmail.proxmox.com>

On November 24, 2020 4:36 pm, Dietmar Maurer wrote:
> Does this improve something? I can't see the purpose of this change.

it allows use to display this remembered fingerprint (e.g., in the 
'invalidating bitmap' message or via the WIP 'query-proxmox-support'.

(also, I'd rather harmonize this now while PVE->PBS is still in beta, 
and not afterwards)

>> @@ -152,7 +154,8 @@ pub(crate) fn check_last_encryption_key(
>>      let digest_guard = PREVIOUS_CRYPT_CONFIG_DIGEST.lock().unwrap();
>>      match (*digest_guard, config)  {
>>          (Some(last_digest), Some(current_config)) => {
>> -            crypt_config_digest(current_config) == last_digest
>> +            current_config.fingerprint().bytes() == &last_digest
>> +                || crypt_config_digest(current_config) == last_digest
>>          },
>>          (None, None) => true,
>>          _ => false,
>> @@ -440,7 +443,13 @@ pub(crate) async fn finish_backup(
>>  
>>      {
>>          let crypt_config_digest = match crypt_config {
>> -            Some(current_config) => Some(crypt_config_digest(current_config)),
>> +            Some(current_config) => {
>> +                let fp = current_config
>> +                    .fingerprint()
>> +                    .bytes()
>> +                    .to_owned();
>> +                Some(fp)
>> +            },
>>              None => None,
>>          };
>>
> 




  reply	other threads:[~2020-11-24 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 13:05 [pbs-devel] [PATCH proxmox-backup(-qemu) 0/3] switch to fingerprint for tracking key Fabian Grünbichler
2020-11-24 13:05 ` [pbs-devel] [PATCH proxmox-backup-qemu 1/2] encryption key tracking: use fingerprint Fabian Grünbichler
2020-11-24 15:36   ` Dietmar Maurer
2020-11-24 15:44     ` Fabian Grünbichler [this message]
2020-11-25  7:28   ` [pbs-devel] applied: " Dietmar Maurer
2020-11-24 13:05 ` [pbs-devel] [PATCH proxmox-backup] fingerprint: add bytes() accessor Fabian Grünbichler
2020-11-25  7:27   ` [pbs-devel] applied: " Dietmar Maurer
2020-11-24 13:05 ` [pbs-devel] [PATCH proxmox-backup-qemu 2/2] fingerprint: rename variables Fabian Grünbichler

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=1606232547.d9bn5hfnnr.astroid@nora.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=dietmar@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal