From: George Dunlap <george.dunlap@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Simon Waterman <watermansrdev@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC 0/6] qemu-xen-trad: sasl: add SASL support to VNC
Date: Tue, 16 May 2017 14:19:06 +0100 [thread overview]
Message-ID: <793fa65b-24ae-b8ed-1ff9-b8039cd51b41@citrix.com> (raw)
In-Reply-To: <22810.64439.866464.136907@mariner.uk.xensource.com>
On 16/05/17 14:16, Ian Jackson wrote:
> George Dunlap writes ("Re: [PATCH RFC 0/6] qemu-xen-trad: sasl: add SASL support to VNC"):
>> Hmm, I don't think this counts as "small patch with simple changes",
>> but I'll let Ian comment.
>
> I'm quite uneasy about this. It seems like the addition of a lot of
> code; effectively, a fork of the SASL code from upstream.
>
> Presumably the real end goal here is something to do with security.
> But I don't think we would want to offer security support for this new
> functionality.
>
> And it might complicate other fixes to qemu-trad, because different
> versions of qemu-trad would need different patches (ie, it might
> complicate backporting existing securit fixes).
>
> Simon: What is stopping you moving to a modern version of qemu ?
I think from his previous query, it was the fact that there is no
suitable stubdom for qemu-upstream.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-16 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 23:03 [PATCH RFC 0/6] qemu-xen-trad: sasl: add SASL support to VNC Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 1/6] qemu-xen-trad: sasl: expose vnc API to SASL auth Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 2/6] qemu-xen-trad: sasl: define SASL auth API Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 3/6] qemu-xen-trad: sasl: implement SASL auth Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 4/6] qemu-xen-trad: sasl: compatibility with vnc.h Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 5/6] qemu-xen-trad: sasl: introduce SASL authentication and encryption layer Simon Waterman
2017-05-15 23:03 ` [PATCH RFC 6/6] qemu-xen-trad: sasl: add SASL option at build time Simon Waterman
2017-05-16 13:11 ` [PATCH RFC 0/6] qemu-xen-trad: sasl: add SASL support to VNC George Dunlap
2017-05-16 13:16 ` Ian Jackson
2017-05-16 13:19 ` George Dunlap [this message]
2017-05-16 13:28 ` Ian Jackson
2017-05-17 18:49 ` Simon Waterman
2017-05-18 14:43 ` Ian Jackson
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=793fa65b-24ae-b8ed-1ff9-b8039cd51b41@citrix.com \
--to=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=watermansrdev@gmail.com \
--cc=xen-devel@lists.xen.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).