From: Jeff Cody <jcody@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: qemu-devel@nongnu.org, berrange@redhat.com,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] block: curl: Allow passing cookies via QCryptoSecret
Date: Tue, 9 May 2017 11:44:39 -0400 [thread overview]
Message-ID: <20170509154439.GA16494@localhost.localdomain> (raw)
In-Reply-To: <f4a22cdebdd0bca6a13a43a2a6deead7f2ec4bb3.1493906281.git.pkrempa@redhat.com>
On Thu, May 04, 2017 at 04:00:06PM +0200, Peter Krempa wrote:
> Since cookies can contain sensitive data (session ID, etc ...) it is
> desired to hide them from the prying eyes of users. Add a possibility to
> pass them via the secret infrastructure.
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1447413
>
> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> ---
> block/curl.c | 24 +++++++++++++++++++++++-
> qapi/block-core.json | 12 ++++++++++--
> 2 files changed, 33 insertions(+), 3 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index 2708d57c2f..483640b14a 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -85,6 +85,7 @@ static CURLMcode __curl_multi_socket_action(CURLM *multi_handle,
> #define CURL_BLOCK_OPT_SSLVERIFY "sslverify"
> #define CURL_BLOCK_OPT_TIMEOUT "timeout"
> #define CURL_BLOCK_OPT_COOKIE "cookie"
> +#define CURL_BLOCK_OPT_COOKIE_SECRET "cookie-secret"
> #define CURL_BLOCK_OPT_USERNAME "username"
> #define CURL_BLOCK_OPT_PASSWORD_SECRET "password-secret"
> #define CURL_BLOCK_OPT_PROXY_USERNAME "proxy-username"
> @@ -624,6 +625,11 @@ static QemuOptsList runtime_opts = {
> .help = "Pass the cookie or list of cookies with each request"
> },
> {
> + .name = CURL_BLOCK_OPT_COOKIE_SECRET,
> + .type = QEMU_OPT_STRING,
> + .help = "ID of secret used as cookie passed with each request"
> + },
> + {
> .name = CURL_BLOCK_OPT_USERNAME,
> .type = QEMU_OPT_STRING,
> .help = "Username for HTTP auth"
> @@ -657,6 +663,7 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags,
> Error *local_err = NULL;
> const char *file;
> const char *cookie;
> + const char *cookie_secret;
> double d;
> const char *secretid;
> const char *protocol_delimiter;
> @@ -693,7 +700,22 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags,
> s->sslverify = qemu_opt_get_bool(opts, CURL_BLOCK_OPT_SSLVERIFY, true);
>
> cookie = qemu_opt_get(opts, CURL_BLOCK_OPT_COOKIE);
> - s->cookie = g_strdup(cookie);
> + cookie_secret = qemu_opt_get(opts, CURL_BLOCK_OPT_COOKIE_SECRET);
> +
> + if (cookie && cookie_secret) {
> + error_setg(errp,
> + "curl driver cannot handle both cookie and cookie secret");
> + goto out_noclean;
> + }
> +
> + if (cookie_secret) {
> + s->cookie = qcrypto_secret_lookup_as_utf8(cookie_secret, errp);
> + if (!s->cookie) {
> + goto out_noclean;
> + }
> + } else {
> + s->cookie = g_strdup(cookie);
> + }
>
> file = qemu_opt_get(opts, CURL_BLOCK_OPT_URL);
> if (file == NULL) {
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 87fb747ab6..b1643d2032 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2782,11 +2782,15 @@
> # "name1=content1; name2=content2;" as explained by
> # CURLOPT_COOKIE(3). Defaults to no cookies.
> #
> +# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
> +# secure way. See @cookie for the format. (since 2.10)
> +#
> # Since: 2.9
> ##
> { 'struct': 'BlockdevOptionsCurlHttp',
> 'base': 'BlockdevOptionsCurlBase',
> - 'data': { '*cookie': 'str' } }
> + 'data': { '*cookie': 'str',
> + '*cookie-secret': 'str'} }
>
> ##
> # @BlockdevOptionsCurlHttps:
> @@ -2801,12 +2805,16 @@
> # @sslverify: Whether to verify the SSL certificate's validity (defaults to
> # true)
> #
> +# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
> +# secure way. See @cookie for the format. (since 2.10)
> +#
> # Since: 2.9
> ##
> { 'struct': 'BlockdevOptionsCurlHttps',
> 'base': 'BlockdevOptionsCurlBase',
> 'data': { '*cookie': 'str',
> - '*sslverify': 'bool' } }
> + '*sslverify': 'bool',
> + '*cookie-secret': 'str'} }
>
> ##
> # @BlockdevOptionsCurlFtp:
> --
> 2.12.2
>
>
Thanks,
Reviewed-by: Jeff Cody <jcody@redhat.com>
Also:
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc block
-Jeff
next prev parent reply other threads:[~2017-05-09 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 14:00 [Qemu-devel] [PATCH] block: curl: Allow passing cookies via QCryptoSecret Peter Krempa
2017-05-04 14:22 ` Eric Blake
2017-05-04 14:34 ` Daniel P. Berrange
2017-05-09 15:06 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-05-09 15:44 ` Jeff Cody [this message]
2017-05-09 19:43 ` Manos Pitsidianakis
2017-05-09 19:52 ` Eric Blake
2017-05-09 20:03 ` Manos Pitsidianakis
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=20170509154439.GA16494@localhost.localdomain \
--to=jcody@redhat.com \
--cc=berrange@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).