search for: defaultkey2

...;trykey1" and "trykey2" against /dev/sda1. This seems OK for me, so you can attempt multiple keys for a device. > And/or you can specify default keys which are tried against each > device (after more specific keys fail), eg: > > tool --key :key:defaultkey1 --key :key:defaultkey2 > > which would try "defaultkey1" and "defaultkey2" against all devices. However I do not see the point in this: IMHO you better make it explicit which key is used for a certain device. Also, this makes it possible so in case of two similar guests like: - /dev/sda1 with...

The first patch fixes a rather serious bug, the second patch allows multiple --key parameters and default parameters. There is a third patch to libguestfs which adds a test, coming up. I did not yet review and fix the documentation. I think we need to centralize it in one place because at the moment the same documentation for --key is copy/pasted all over the tools. Rich.

You can specify default keys which are tried against each device (after more specific keys fail), eg: tool --key :key:defaultkey1 --key :key:defaultkey2 which would try "defaultkey1" and "defaultkey2" against all devices in the guest. --- options/keys.c | 3 ++- options/options.h | 5 ++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/options/keys.c b/options/keys.c index 782bdb6..817508b 100644 --- a/opti...

...ot; against /dev/sda1. > > This seems OK for me, so you can attempt multiple keys for a device. > > > And/or you can specify default keys which are tried against each > > device (after more specific keys fail), eg: > > > > tool --key :key:defaultkey1 --key :key:defaultkey2 > > > > which would try "defaultkey1" and "defaultkey2" against all devices. > > However I do not see the point in this: IMHO you better make it explicit > which key is used for a certain device. It's considerably more convenient for callers if they d...

v1: https://www.redhat.com/archives/libguestfs/2019-November/msg00036.html

...as: tool --key /dev/sda1:key:trykey1 --key /dev/sda1:key:trykey2 which would try "trykey1" and "trykey2" against /dev/sda1. And/or you can specify default keys which are tried against each device (after more specific keys fail), eg: tool --key :key:defaultkey1 --key :key:defaultkey2 which would try "defaultkey1" and "defaultkey2" against all devices. --- options/decrypt.c | 41 ++++++++++++++++++----- options/keys.c | 83 +++++++++++++++++++++++++++++------------------ options/options.h | 8 +++-- 3 files changed, 89 insertions(+), 43 deletions(-) di...

...n be retrieved from lsblk and blkid. My 2 cents. On Tue, Nov 26, 2019 at 5:44 PM Richard W.M. Jones <rjones@redhat.com> wrote: > You can specify default keys which are tried against each device > (after more specific keys fail), eg: > > tool --key :key:defaultkey1 --key :key:defaultkey2 > > which would try "defaultkey1" and "defaultkey2" against all devices > in the guest. > --- > options/keys.c | 3 ++- > options/options.h | 5 ++++- > 2 files changed, 6 insertions(+), 2 deletions(-) > > diff --git a/options/keys.c b/options/keys...

...gt; > This seems OK for me, so you can attempt multiple keys for a device. > > > > > And/or you can specify default keys which are tried against each > > > device (after more specific keys fail), eg: > > > > > > tool --key :key:defaultkey1 --key :key:defaultkey2 > > > > > > which would try "defaultkey1" and "defaultkey2" against all devices. > > > > However I do not see the point in this: IMHO you better make it explicit > > which key is used for a certain device. > > It's considerably mo...