| commit | 1cd9a787a2ee519665d914193e1022791397d621 | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Fri, 23 Jun 2017 16:24:17 +0000 (23 17:24 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Tue, 11 Jul 2017 15:44:56 +0000 (11 17:44 +0200) | ||
| tree | ee746c7f8e55e999435222c07cac64df65e7ee88 | treesnapshot (tar.gz zip) |
| parent | c01c214b691d2f9c54a15ea7e486b1750f20fbf8 | commitdiff |
block: pass option prefix down to crypto layer
While the crypto layer uses a fixed option name "key-secret",
the upper block layer may have a prefix on the options. e.g.
"encrypt.key-secret", in order to avoid clashes between crypto
option names & other block option names. To ensure the crypto
layer can report accurate error messages, we must tell it what
option name prefix was used.
Reviewed-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170623162419.26068-19-berrange@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
While the crypto layer uses a fixed option name "key-secret",
the upper block layer may have a prefix on the options. e.g.
"encrypt.key-secret", in order to avoid clashes between crypto
option names & other block option names. To ensure the crypto
layer can report accurate error messages, we must tell it what
option name prefix was used.
Reviewed-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170623162419.26068-19-berrange@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>