All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: xen-devel@lists.xensource.com
Subject: PATCH: 0/4: TLS encryption and x509 authentication for VNC
Date: Mon, 29 Oct 2007 21:48:58 +0000	[thread overview]
Message-ID: <20071029214858.GG1053@redhat.com> (raw)

The following series of patches sync the VNC authentication support in Xen's
fork of QEMU, to match the latest upstream QEMU. This is to enable the new
VeNCrypt protocol extension which provides for TLS enryption and x509 auth
in the VNC server. This extension can be used by client programs such as the
GTK-VNC widget[1], virt-viewer/virt-manager[2], and the VeNCrypt viewer[3]
Since these patches are already upstream, they will go away next time we
re-base QEMU in Xen, and thus have minimal long term maintainence pain,
compared to current auth code which is not upstream.

Regards,
Dan.

[1] http://gtk-vnc.sourceforge.net
[2] http://virt-manager.org/
[3] http://sourceforge.net/projects/vencrypt/
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

             reply	other threads:[~2007-10-29 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 21:48 Daniel P. Berrange [this message]
2007-10-29 21:51 ` PATCH: 1/4: QEMU event handler bug fix Daniel P. Berrange
2007-10-29 21:51 ` PATCH: 2/4: Revert current VNC auth support Daniel P. Berrange
2007-10-29 21:52 ` PATCH: 3/4: Add VNC auth support from upstream QEMU Daniel P. Berrange
2007-10-30  7:53   ` Pasi Kärkkäinen
2007-10-30 13:31     ` Daniel P. Berrange
2007-10-29 21:53 ` PATCH: 4/4: XenD config for VNC TLS protocol 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=20071029214858.GG1053@redhat.com \
    --to=berrange@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.