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

Re: [Xen-users] console access for domU owners


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Stephen Le <zeroion@xxxxxxxxx>
  • Date: Sun, 16 Oct 2005 07:04:12 -0700
  • Delivery-date: Mon, 17 Oct 2005 08:50:12 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BMEqD6fxKlRID9o76dWVf0ByxDGtTopnTchiTznOx+vzKUdrCiMf+Us/aTWIB4enFedIG2RyvKe4XKqVgjajTnmZ61NtxgMH63PUTlcWJy7gr/nJEZzj3REyipQWdF6C+urAZKjaLvTBh8r5KLsDuQnscvG749UmJfAZFQhS0Oc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 10/16/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> You can use ssh's forced command facility to allow suitably
> authenticated users to connect to the console on a particular vm.

>From what I've read, it appears that SSH's forced command facility
only works with public key authentication. Given the difficulties of
getting every user to generate a SSH auth key and of managing them, I
don't think such a solution would be very practical.

It appears that my best hope is using, as a login shell, a script that
calls telnet. The script will determine the UID, lookup the
appropriate console port, and launch a telnet session (with the escape
character disabled).

Anybody see anything wrong with that?

_______________________________________________
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®.