From: Blue Swirl <blauwirbel@gmail.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 20:57:39 +0200 [thread overview]
Message-ID: <f43fc5580902261057w31e4156ar9885ed14bc72e11f@mail.gmail.com> (raw)
In-Reply-To: <20090226115624.GL22494@redhat.com>
On 2/26/09, Daniel P. Berrange <berrange@redhat.com> wrote:
> This patch adds the new SASL authentication protocol to the VNC server.
> @@ -2436,7 +2531,7 @@ QEMU emulates the following PowerMac per
>
> @itemize @minus
> @item
> -UniNorth or Grackle PCI Bridge
> +UniNorth PCI Bridge
> @item
> PCI VGA compatible card with VESA Bochs Extensions
> @item
> @@ -2474,9 +2569,9 @@ QEMU uses the Open Hack'Ware Open Firmwa
> @url{http://perso.magic.fr/l_indien/OpenHackWare/index.htm}.
>
> Since version 0.9.1, QEMU uses OpenBIOS @url{http://www.openbios.org/}
> -for the g3beige and mac99 PowerMac machines. OpenBIOS is a free (GPL
> -v2) portable firmware implementation. The goal is to implement a 100%
> -IEEE 1275-1994 (referred to as Open Firmware) compliant firmware.
> +for the g3beige PowerMac machine. OpenBIOS is a free (GPL v2) portable
> +firmware implementation. The goal is to implement a 100% IEEE
> +1275-1994 (referred to as Open Firmware) compliant firmware.
>
> @c man begin OPTIONS
>
> @@ -2705,7 +2800,7 @@ PCnet32 PCI network card
> @item
> Malta FPGA serial device
> @item
> -Cirrus (default) or any other PCI VGA graphics card
> +Cirrus VGA graphics card
> @end itemize
>
> The ACER Pica emulation supports:
Please remove these changes.
next prev parent reply other threads:[~2009-02-26 18:57 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 [this message]
2009-02-26 20:33 ` Daniel P. Berrange
2009-02-26 21:34 ` Anthony Liguori
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=f43fc5580902261057w31e4156ar9885ed14bc72e11f@mail.gmail.com \
--to=blauwirbel@gmail.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).