From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] PATCH: 0/9: Support SASL authentication in VNC server (version 4)
Date: Mon, 2 Mar 2009 12:31:21 +0000 [thread overview]
Message-ID: <20090302123121.GH15108@redhat.com> (raw)
Previously I provided patches for QEMU's VNC server to support SSL/TLS
and x509 certificates. This provides good encryption capabilities for
the VNC session. It doesn't really address the authentication problem
though.
I have been working to create a new authentication type in the RFB
protocol to address this need in a generic, extendable way, by mapping
the SASL API into the RFB protocol. Since SASL is a generic plugin
based API, this will allow use of a huge range of auth mechanims over
VNC, without us having to add any more auth code. For example, PAM,
Digest-MD5, GSSAPI/Kerberos, One-time key/password, LDAP password
lookup, SQL db password lookup, and more.
I have got a VNC auth type assigned by the RFB spec maintainers:
http://realvnc.com/pipermail/vnc-list/2008-December/059463.html
With the full current spec for the SASL extension currently documented
here:
http://realvnc.com/pipermail/vnc-list/2008-December/059462.html
This is the 4th version of the patches I previously posted:
v1: http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg00255.html
v2: http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg00826.html
v3: http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg01418.html
Changes since last time
- Removed mistaken changes to qemu-doc.texi from bad merge
- Renamed the 'ACL' struct to 'qemu_acl' to avoid clash with
a system header typedef in Win32 platforms
- Check for 'fnmatch' function in configure, and if not found
then revert to exact strcmp() matching instead of wildcard
matching
- Add docs for the 'acl' monitor command
The combined diffstat for all 9 patches is
Makefile | 27 +
Makefile.target | 5
b/acl.c | 298 +++++++++++++
b/acl.h | 77 +++
b/keymaps.h | 60 ++
b/qemu.sasl | 34 +
b/vnc-auth-sasl.c | 636 ++++++++++++++++++++++++++++
b/vnc-auth-sasl.h | 74 +++
b/vnc-auth-vencrypt.c | 175 +++++++
b/vnc-auth-vencrypt.h | 33 +
b/vnc-tls.c | 450 ++++++++++++++++++++
b/vnc-tls.h | 76 +++
configure | 52 ++
curses.c | 3
curses_keys.h | 9
keymaps.c | 45 --
monitor.c | 95 ++++
qemu-doc.texi | 146 ++++++
sdl.c | 3
sdl_keysym.h | 7
vl.c | 12
vnc.c | 1117 ++++++++++++++++++--------------------------------
vnc.h | 229 +++++++++-
vnc_keysym.h | 7
24 files changed, 2908 insertions(+), 762 deletions(-)
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next reply other threads:[~2009-03-02 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 12:31 Daniel P. Berrange [this message]
2009-03-02 12:39 ` [Qemu-devel] PATCH: 1/9: Fix bug in TLS authentication Daniel P. Berrange
2009-03-02 12:39 ` [Qemu-devel] PATCH: 2/9: Enhance 'info vnc' monitor output Daniel P. Berrange
2009-03-02 12:39 ` [Qemu-devel] PATCH: 3/9: Refactor keymap code to avoid duplication Daniel P. Berrange
2009-03-02 12:40 ` [Qemu-devel] PATCH: 4/9: Move VNC structs into header file Daniel P. Berrange
2009-03-02 12:40 ` [Qemu-devel] PATCH: 5/9: Move TLS auth into separate file Daniel P. Berrange
2009-03-02 12:41 ` [Qemu-devel] PATCH: 6/9: Add SASL authentication support Daniel P. Berrange
2009-03-02 12:41 ` [Qemu-devel] PATCH: 7/9: Include auth credentials in 'info vnc' Daniel P. Berrange
2009-03-02 12:42 ` [Qemu-devel] PATCH: 8/9: Support ACLs for controlling VNC access Daniel P. Berrange
2009-03-02 12:42 ` [Qemu-devel] PATCH: 9/9: Persist ACLs in external files Daniel P. Berrange
2009-03-02 12:49 ` [Qemu-devel] PATCH: 0/9: Support SASL authentication in VNC server (version 4) Daniel P. Berrange
2009-03-06 20:30 ` Anthony Liguori
2009-03-09 9:51 ` 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=20090302123121.GH15108@redhat.com \
--to=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).