[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN domUs and X11 (maybe not Xen-related)


  • To: Javier Guerra Giraldez <javier@xxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Fri, 18 Jan 2008 06:36:40 +0000
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 17 Jan 2008 22:37:17 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=hQkrFGebP+FGRknNxAoFdhMBiY+0xR73dk2eJA9G5Vi/VFZh6kHrpnhsMXx/KkujP/C8SFdp30F3zniDkAQGJKQsGlyw+5178nsXtGwnbL7zXdAybGuMuyn+iFduzBeNFBmUEoX/YdTPLF8dIv/9UUl9GaXf1vId3rw3N60bhus=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Javier Guerra Giraldez wrote:
On Thursday 17 January 2008, Nico Kadel-Garcia wrote:
This is a serious security issue with lots of VNC based tools, such as
most remote KVM's. It mandates that you use a good screenlock on the VNC
server's X session, in case you walk away and come back. Xen default
setups attempt to deal with this somewhat by restricting those VNC
clients to access from the Dom0 itself. But woe betide the admin who
opens it up for remote management and fails to protect their X session!

being a non-encrypted protocol, i guess anyone that uses it remotely without some kind of VPN is already exposing too much.

Oh, goodness, yes. The VNC password is exchanged encrypted, but passwords after that are.... at some small risk. This is why a thoughtful and secure admin will SSH to the Dom0 and run VNC locally in an X session, although that imposes some additional computational burdens on Dom0

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.