From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
qemu-block@nongnu.org, Josh Durgin <jdurgin@redhat.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] iscsi: add support for getting CHAP password via QCryptoSecret API
Date: Mon, 21 Dec 2015 16:58:41 +0100 [thread overview]
Message-ID: <567821B1.9060907@redhat.com> (raw)
In-Reply-To: <1450709966-2998-4-git-send-email-berrange@redhat.com>
On 21/12/2015 15:59, Daniel P. Berrange wrote:
> The iSCSI driver currently accepts the CHAP password in plain text
> as a block driver property. This change adds a new "passwordid"
> property that accepts the ID of a QCryptoSecret instance.
>
> $QEMU \
> -object secret,id=sec0,filename=/home/berrange/example.pw \
> -drive driver=iscsi,url=iscsi://example.com/target-foo/lun1,\
> user=dan,passwordid=sec0
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> block/iscsi.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/block/iscsi.c b/block/iscsi.c
> index bd1f1bf..96fa3e1 100644
> --- a/block/iscsi.c
> +++ b/block/iscsi.c
> @@ -39,6 +39,7 @@
> #include "sysemu/sysemu.h"
> #include "qmp-commands.h"
> #include "qapi/qmp/qstring.h"
> +#include "crypto/secret.h"
>
> #include <iscsi/iscsi.h>
> #include <iscsi/scsi-lowlevel.h>
> @@ -1075,6 +1076,8 @@ static void parse_chap(struct iscsi_context *iscsi, const char *target,
> QemuOpts *opts;
> const char *user = NULL;
> const char *password = NULL;
> + const char *passwordid;
> + char *secret = NULL;
>
> list = qemu_find_opts("iscsi");
> if (!list) {
> @@ -1094,8 +1097,20 @@ static void parse_chap(struct iscsi_context *iscsi, const char *target,
> return;
> }
>
> + passwordid = qemu_opt_get(opts, "passwordid");
> password = qemu_opt_get(opts, "password");
> - if (!password) {
> + if (passwordid && password) {
> + error_setg(errp, "'password' and 'passwordid' properties are "
> + "mutually exclusive");
> + return;
> + }
> + if (passwordid) {
> + secret = qcrypto_secret_lookup_as_utf8(passwordid, errp);
I'm not sure about the UTF-8 part (it should be binary), but I think we
discussed this already. Apart from this, the patch is okay.
Paolo
> + if (!secret) {
> + return;
> + }
> + password = secret;
> + } else if (!password) {
> error_setg(errp, "CHAP username specified but no password was given");
> return;
> }
> @@ -1103,6 +1118,8 @@ static void parse_chap(struct iscsi_context *iscsi, const char *target,
> if (iscsi_set_initiator_username_pwd(iscsi, user, password)) {
> error_setg(errp, "Failed to set initiator username and password");
> }
> +
> + g_free(secret);
> }
>
> static void parse_header_digest(struct iscsi_context *iscsi, const char *target,
> @@ -1848,6 +1865,11 @@ static QemuOptsList qemu_iscsi_opts = {
> .type = QEMU_OPT_STRING,
> .help = "password for CHAP authentication to target",
> },{
> + .name = "passwordid",
> + .type = QEMU_OPT_STRING,
> + .help = "ID of the secret providing password for CHAP "
> + "authentication to target",
> + },{
> .name = "header-digest",
> .type = QEMU_OPT_STRING,
> .help = "HeaderDigest setting. "
>
next prev parent reply other threads:[~2015-12-21 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 14:59 [Qemu-devel] [PATCH v2 0/3] Use QCryptoSecret for block device passwords Daniel P. Berrange
2015-12-21 14:59 ` [Qemu-devel] [PATCH v2 1/3] rbd: add support for getting password from QCryptoSecret object Daniel P. Berrange
2015-12-21 15:57 ` Josh Durgin
2015-12-21 14:59 ` [Qemu-devel] [PATCH v2 2/3] curl: add support for HTTP authentication parameters Daniel P. Berrange
2015-12-21 14:59 ` [Qemu-devel] [PATCH v2 3/3] iscsi: add support for getting CHAP password via QCryptoSecret API Daniel P. Berrange
2015-12-21 15:58 ` Paolo Bonzini [this message]
2015-12-21 16:17 ` Daniel P. Berrange
2016-01-11 15:12 ` [Qemu-devel] [PATCH v2 0/3] Use QCryptoSecret for block device passwords Markus Armbruster
2016-01-11 15:28 ` Daniel P. Berrange
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=567821B1.9060907@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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;
as well as URLs for NNTP newsgroup(s).