From: Christophe Fergeau <cfergeau@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 2/2] Error out when tls-channel option is used without TLS
Date: Fri, 24 Feb 2012 11:37:54 +0100 [thread overview]
Message-ID: <1330079874-5818-2-git-send-email-cfergeau@redhat.com> (raw)
In-Reply-To: <1330079874-5818-1-git-send-email-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.
---
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 6d240a3..5e644c9 100644
--- a/ui/spice-core.c
+++ b/ui/spice-core.c
@@ -524,8 +524,11 @@ static int add_channel(const char *name, const char *value, void *opaque)
{
int security = 0;
int rc;
+ int *tls_port = opaque;
if (strcmp(name, "tls-channel") == 0) {
+ if (!*tls_port)
+ return 1;
security = SPICE_CHANNEL_SECURITY_SSL;
}
if (strcmp(name, "plaintext-channel") == 0) {
@@ -697,7 +700,10 @@ 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);
+ if (qemu_opt_foreach(opts, add_channel, &tls_port, 1) != 0) {
+ fprintf(stderr, "tried to setup tls-channel without specifying a TLS port\n");
+ exit(1);
+ }
if (0 != spice_server_init(spice_server, &core_interface)) {
fprintf(stderr, "failed to initialize spice server\n");
--
1.7.7.6
next prev parent reply other threads:[~2012-02-24 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 10:37 [Qemu-devel] [PATCH 1/2] Add \n to the end of fatal spice error messages Christophe Fergeau
2012-02-24 10:37 ` Christophe Fergeau [this message]
2012-02-24 16:49 ` [Qemu-devel] [PATCH 2/2] Error out when tls-channel option is used without TLS Gerd Hoffmann
2012-02-24 16:47 ` [Qemu-devel] [PATCH 1/2] Add \n to the end of fatal spice error messages Gerd Hoffmann
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=1330079874-5818-2-git-send-email-cfergeau@redhat.com \
--to=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).