qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	Christophe Fergeau <cfergeau@redhat.com>
Subject: [Qemu-devel] [PATCH 10/11] Error out when tls-channel option is used without TLS
Date: Tue, 28 Feb 2012 17:30:01 +0100	[thread overview]
Message-ID: <1330446602-10743-11-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1330446602-10743-1-git-send-email-kraxel@redhat.com>

From: Christophe Fergeau <cfergeau@redhat.com>

It's currently possible to setup spice channels using TLS when
no TLS port has been specified (ie TLS is disabled). This cannot
work, so better to error out in such a situation.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 ui/spice-core.c |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/ui/spice-core.c b/ui/spice-core.c
index e761813..c1091e1 100644
--- a/ui/spice-core.c
+++ b/ui/spice-core.c
@@ -511,6 +511,12 @@ static int add_channel(const char *name, const char *value, void *opaque)
     int rc;
 
     if (strcmp(name, "tls-channel") == 0) {
+        int *tls_port = opaque;
+        if (!*tls_port) {
+            error_report("spice: tried to setup tls-channel"
+                         " without specifying a TLS port");
+            exit(1);
+        }
         security = SPICE_CHANNEL_SECURITY_SSL;
     }
     if (strcmp(name, "plaintext-channel") == 0) {
@@ -680,7 +686,7 @@ void qemu_spice_init(void)
     spice_server_set_playback_compression
         (spice_server, qemu_opt_get_bool(opts, "playback-compression", 1));
 
-    qemu_opt_foreach(opts, add_channel, NULL, 0);
+    qemu_opt_foreach(opts, add_channel, &tls_port, 0);
 
     if (0 != spice_server_init(spice_server, &core_interface)) {
         error_report("failed to initialize spice server");
-- 
1.7.1

  parent reply	other threads:[~2012-02-28 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 16:29 [Qemu-devel] [PULL] spice patch queue Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 01/11] qxl: fix spice+sdl no cursor regression Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 02/11] sdl: remove NULL check, g_malloc0 can't fail Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 03/11] qxl: drop qxl_spice_update_area_async definition Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 04/11] qxl: require spice >= 0.8.2 Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 05/11] qxl: remove flipped Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 06/11] qxl: introduce QXLCookie Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 07/11] qxl: make qxl_render_update async Gerd Hoffmann
2012-02-28 16:29 ` [Qemu-devel] [PATCH 08/11] qxl: add optinal 64bit vram bar Gerd Hoffmann
2012-02-28 16:30 ` [Qemu-devel] [PATCH 09/11] spice: use error_report to report errors Gerd Hoffmann
2012-02-28 16:30 ` Gerd Hoffmann [this message]
2012-02-28 16:30 ` [Qemu-devel] [PATCH 11/11] qxl: properly handle upright and non-shared surfaces Gerd Hoffmann
2012-02-29 21:07 ` [Qemu-devel] [PULL] spice patch queue Anthony Liguori

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=1330446602-10743-11-git-send-email-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=cfergeau@redhat.com \
    --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).