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

[Xen-users] Username Parameter in the Xen Config File

  • To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Omer Khalid" <Omer.Khalid@xxxxxxx>
  • Date: Wed, 10 Oct 2007 16:11:47 +0200
  • Delivery-date: Wed, 10 Oct 2007 07:12:33 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=PcrcvauVpmfcI1S7VusG7E9zECgnqZ9gHTm83J1yfJN6eBgPZG+wv1zPVrqpztRTDiCxlmK0GAscpoWKER8s4/auig2V4BDdno2tpC+7iZfUdsmyOsVJKciQMnbDv17CK524TbfzOCxzyF762aa0Ig0LhkieQDG2uXY3+Z69Cec=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


We have been using xen virtualization for some time now on our gLite certification test bed, and have stumbled upon an issue which requires some clever tricks.

We have X number of users for our test bed, and for the moment we have kept their SSH keys in the /root/.ssh/authorized_keys file on the images. Now we would like to restrict access to the user who deployed the virtual machine. I am wondering if it's possible to pass some kind of shell script or another username parameter in the xen configuration file to execute when the image boots up.

Any ideas? Thanks for your help!


CERN – European Organization for Nuclear
Research, IT Department,  CH-1211
Geneva 23, Switzerland

Phone: +41 (0) 22 767 2224
Fax:     +41 (0) 22 766 8683
E-mail : Omer.Khalid@xxxxxxx
Homepage: http://cern.ch/Omer.Khalid
Xen-users mailing list



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