qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: 6/9: Add SASL authentication support
Date: Thu, 26 Feb 2009 15:34:58 -0600	[thread overview]
Message-ID: <49A70B02.3040106@us.ibm.com> (raw)
In-Reply-To: <20090226115624.GL22494@redhat.com>

Daniel P. Berrange wrote:
> diff -r 0eb0b12c0673 qemu-doc.texi
> --- a/qemu-doc.texi	Mon Feb 23 13:06:22 2009 +0000
> +++ b/qemu-doc.texi	Mon Feb 23 13:40:03 2009 +0000
> @@ -616,6 +616,21 @@ path following this option specifies whe
>  be loaded from. See the @ref{vnc_security} section for details on generating
>  certificates.
>  
> +@item sasl
> +
> +Require that the client use SASL to authenticate with the VNC server.
> +The exact choice of authentication method used is controlled from the
> +system / user's SASL configuration file for the 'qemu' service. This
> +is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
> +unprivileged user, an environment variable SASL_CONF_PATH can be used
> +to make it search alternate locations for the service config.
> +While some SASL auth methods can also provide data encryption (eg GSSAPI),
> +it is recommended that SASL always be combined with the 'tls' and
> +'x509' settings to enable use of SSL and server certificates. This
> +ensures a data encryption preventing compromise of authentication
> +credentials. See the @ref{vnc_security} section for details on using
> +SASL authentication.
> +
>  @end table
>  
>  @end table
> @@ -964,8 +979,6 @@ This implements UDP Net Console.
>  When @var{remote_host} or @var{src_ip} are not specified
>  they default to @code{0.0.0.0}.
>  When not using a specified @var{src_port} a random port is automatically chosen.
> -@item msmouse
> -Three button serial mouse. Configure the guest to use Microsoft protocol.
>  
>  If you just want a simple readonly console you can use @code{netcat} or
>  @code{nc}, by starting qemu with: @code{-serial udp::4555} and nc as:
>   

That removal looks like a mistake to me.  I'm going to remove it from 
your patch.

Regards,

Anthony Liguori

  parent reply	other threads:[~2009-02-26 21:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 11:39 [Qemu-devel] PATCH: 0/9: Support SASL authentication in VNC server (version 3) Daniel P. Berrange
2009-02-26 11:52 ` [Qemu-devel] PATCH: 1/9: Fix bug in TLS authenticataion Daniel P. Berrange
2009-02-26 11:52 ` [Qemu-devel] PATCH: 2/9: Enhance 'info vnc' monitor output Daniel P. Berrange
2009-02-26 11:53 ` [Qemu-devel] PATCH: 3/9: Refactor keymap code to avoid duplication Daniel P. Berrange
2009-02-26 11:53 ` [Qemu-devel] PATCH: 4/9: Move VNC structs into header file Daniel P. Berrange
2009-02-26 11:55 ` [Qemu-devel] PATCH: 5/9: Move TLS auth into separate file Daniel P. Berrange
2009-02-26 11:56 ` [Qemu-devel] PATCH: 6/9: Add SASL authentication support Daniel P. Berrange
2009-02-26 18:57   ` Blue Swirl
2009-02-26 20:33     ` Daniel P. Berrange
2009-02-26 21:34   ` Anthony Liguori [this message]
2009-02-27 10:46   ` Daniel P. Berrange
2009-02-27 11:14     ` John Haxby
2009-02-26 11:56 ` [Qemu-devel] PATCH: 7/9: Include auth credentials in 'info vnc' Daniel P. Berrange
2009-02-26 11:57 ` [Qemu-devel] PATCH: 8/9: Support ACLs for controlling VNC access Daniel P. Berrange
2009-02-26 22:05   ` Anthony Liguori
2009-02-26 22:07   ` Anthony Liguori
2009-02-27 10:42     ` Daniel P. Berrange
2009-02-26 11:57 ` [Qemu-devel] PATCH: 9/9: Persist ACLs in external files Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2009-03-02 12:31 [Qemu-devel] PATCH: 0/9: Support SASL authentication in VNC server (version 4) Daniel P. Berrange
2009-03-02 12:41 ` [Qemu-devel] PATCH: 6/9: Add SASL authentication support Daniel P. Berrange

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=49A70B02.3040106@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=berrange@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).