Attachment 119591 Details for Bug 92918 – Use correct SASL service name

[patch] Use correct SASL service name

0001-Use-correct-SASL-service-name.patch (text/plain), 1.48 KB, created by Marek Kasik on 2015-11-12 14:18:17 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marek Kasik

Created: 2015-11-12 14:18:17 UTC

Size: 1.48 KB

patch

obsolete

>From 7ff8cb56acdbc747edec26370e143878822db253 Mon Sep 17 00:00:00 2001
>From: Marek Kasik <mkasik@redhat.com>
>Date: Thu, 12 Nov 2015 15:10:31 +0100
>Subject: [PATCH] Use correct SASL service name
>
>Use "qemu" service name when using SASL. GSSAPI uses this name
>when issuing tickets and there is no "spice" service yet.
>---
> server/reds.c        | 2 +-
> server/reds_stream.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/server/reds.c b/server/reds.c
>index 1f6774e..79008ff 100644
>--- a/server/reds.c
>+++ b/server/reds.c
>@@ -3329,7 +3329,7 @@ static int do_spice_init(SpiceCoreInterface *core_interface)
> #if HAVE_SASL
>     int saslerr;
>     if ((saslerr = sasl_server_init(NULL, sasl_appname ?
>-                                    sasl_appname : "spice")) != SASL_OK) {
>+                                    sasl_appname : "qemu")) != SASL_OK) {
>         spice_error("Failed to initialize SASL auth %s",
>                   sasl_errstring(saslerr, NULL, NULL));
>         goto err;
>diff --git a/server/reds_stream.c b/server/reds_stream.c
>index 3b47391..9b3ab3a 100644
>--- a/server/reds_stream.c
>+++ b/server/reds_stream.c
>@@ -971,7 +971,7 @@ bool reds_sasl_start_auth(RedsStream *stream, AsyncReadDone read_cb, void *opaqu
>         goto error;
>     }
> 
>-    err = sasl_server_new("spice",
>+    err = sasl_server_new("qemu",
>                           NULL, /* FQDN - just delegates to gethostname */
>                           NULL, /* User realm */
>                           localAddr,
>-- 
>2.5.0
>

Actions: View | Splinter Review

Attachments on bug 92918: 119591 | 119592

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.