From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Wed 28 Apr 2004 - 15:50:43 BST
On Wed, Apr 28, 2004 at 01:56:33PM +0200, Brian wrote:
> Hello list,
> I run to test the software vservers on my Laptop. It's run well !!
> Now I install a Server with the vserver Software.
> I't run but when I connect with ssh to the vserver IP I'm on the host file
> for example
> the host is called "v-host" and the virtual server "vserver2". my notebook
> is called "schleppy"
> v-host:/vservers# vserver vserver2 start
> Starting the virtual server vserver2
> Server vserver2 is not running
> ipv4root is now 192.168.141.17
> Host name is now vserver2
> New security context is 49154
> Starting system log daemon: syslogd.
> Starting kernel log daemon: klogd.
> Starting internet superserver: inetd.
> Starting OpenBSD Secure Shell server: sshd.
> Starting deferred execution scheduler: atd.
> Starting periodic command scheduler: cron.
> schleppy:/# ssh root_at_192.168.141.17
> The authenticity of host '192.168.141.17 (192.168.141.17)' can't be
> RSA key fingerprint is d1:c2:c4:2a:c1:02:51:92:c0:75:38:8c:15:3a:29:17.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added '192.168.141.17' (RSA) to the list of known
> Last login: Wed Apr 28 14:23:43 2004 from schleppy.linux.local
> v-host:~# <<<<< YOU SEE, I'M ON "V-HOST", NOT ON VSERVER2
well, while the shell prompt isn't the best way
to tell if it's the host or the vserver, I'd say
your hosts's sshd is still bound to all possible
addresses (aka as IPADDR_ANY or 0.0.0.0) and so
jsut intercepts your ongoing ssh connection, which
provided that the password for both accounts is
the same, will look like the vserver sshd did put
you on the host's root filesystem ...
> anyone know this ?
> Vserver mailing list
Vserver mailing list