Re[2]: [Openvds-support] ssh/ftp

[River Hume]

> Your looking in ssh_config not the sshd_config file.. That little d
> makes a big difference..
> Check again..

Whoops! heh, thanx... sorry. Yes, the ip is correctly listed. here is the 
passage from that file:

# This is ssh server systemwide configuration file.

Port 22
Protocol 2,1
ListenAddress 208.253.112.82
#ListenAddress ::
HostKey /etc/ssh/ssh_host_key
HostDsaKey /etc/ssh/ssh_host_dsa_key
DSAAuthentication yes
ServerKeyBits 768
LoginGraceTime 600
KeyRegenerationInterval 3600
PermitRootLogin no
#

One thing I noticed however, in the master server's sshd_config file, the 
ip listed is not the one the domain name points to, but rather the MASTER 
ip which as far as I know remains invisible (not even declared in 
etc/hosts), and unknown to any but myself and a few others... I don't even 
know how it could be answering to our domain name from the looks of it 
though... Could this somehow be causing it to listen to all traffic on the 
server? It doesn't really make any sense... :(

> That is what vsdadm does. And why your really should setup the web
> interface which uses the vsdadm tool featureset to do this.
> Also my guess would be that your userid for admin for this VS is not
> 500 and you have a user of admin on the main system.
> vsdadm vs_details masterserver-hostname virtualservername
> Check the uid=xxxx that is the uid of your admin for that skel.
> If you want to give the admin for that skel access to edit the file
> you need to do
> chmod xxxx.xxxx /home/vsd/vs/virtualservername/etc/vsd/priv
> where xxxx equals the xxxx from the uid provided by vs_details.

Thanx :) This sheds much light on how vsd works with users on virtual 
servers...

> The webadmin is a tool to give virtual server owners access to their
> virtual server to change apache config, add users, change sendmail
> options, alter quotas, alter the /etc/priv file (which is the done
> through the vsdadm protocol). This tool runs on the master server.
>
> If the VS owner want to resell and host other peoples he will have to
> setup accounts and fix apache since the webadmin tool grants "full"
> access to the entire VS he's given access to.
> This also gives the VS admin the ability to reboot HIS ENTIRE VS just
> like if root on the master server did "vsboot --restart VS" or
> "vsdadm vs_reboot <host svr> [<vs>]"

Does it even run on svsd? According to the readme on freevsd.org:

The file VSDWebAdmin1.4.5.tar.gz contains the WebAdmin scripts for 
administration of Virtual Servers running under freeVSD V1.4.5 - V1.4.6

and the website claims that it is for use only on non svsd installs... Has 
anyone tried it with 1.4.10? is anyone interested in fixing it so it will 
work with 1.4.10 if not? As I mentioned earlier, I would GLADLY help fix 
the code, if I could get a little direction as to what specifically needs 
fixing.