All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Luke-Jr <luke@dashjr.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: Secure TLS encrypted authentication for VNC
Date: Sat, 24 Feb 2007 19:00:30 +0000	[thread overview]
Message-ID: <20070224190030.GA21828@redhat.com> (raw)
In-Reply-To: <200702241857.18867.luke@dashjr.org>

On Sat, Feb 24, 2007 at 06:57:16PM +0000, Luke-Jr wrote:
> On Saturday 24 February 2007 04:54:44 pm Daniel P. Berrange wrote:
> > Having repeatedly said that we should be doing TLS encryption for VNC, I
> > figured I ought to get down & implement it. So, in the spirit of 'release
> > early, release often', here is the very first cut of my patch for QEMU.
> > This isn't suitable for inclusion in CVS yet - I just want to put it out
> > for people to see / experiment with.
> 
> Do any Java applets support this? Preferably with an applet 'param' for a 
> private key authentication?

I've not tested it, but the VeNCrypt project have also patched the RealVNC
java client to support the TLS auth extensions.

Regards,
Dan.
-- 
|=- 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-02-24 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 16:54 [Qemu-devel] PATCH: Secure TLS encrypted authentication for VNC Daniel P. Berrange
2007-02-24 18:57 ` Luke-Jr
2007-02-24 19:00   ` Daniel P. Berrange [this message]
2007-02-28 21:27 ` [Qemu-devel] " S. I. Becker
2007-03-01 16:34   ` Daniel P. Berrange
2007-03-01 18:21     ` S. I. Becker

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=20070224190030.GA21828@redhat.com \
    --to=berrange@redhat.com \
    --cc=luke@dashjr.org \
    --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 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.