virtuald performs a lookup within vsd.conf to determine if a connection to a virtual server is allowed (so virtual servers can be disabled) and then chroots into the relevant file system. If the request is directed at the host server that request too is chrooted but because of the 'loopback' entry (see the soft link beneath /home/vsd/vs) it operates on the hosting server's own file system. With this mechanism it is feasible to place freevsd within virtual server's themselves and use freevsd commands to manage a stand-alone server's Apache/Sendmail/Users.
Virtual domains and virtual users currently only have any meaning when applied to mail. They were introduced to allow domain specific passwd files and avoid virtual domain owners having to call their mail-box accounts '[EMAIL PROTECTED]' to avoid a name-clash with bobs in other domains hosted on the same virtual server. It would be posible to patch proftpd to support logging in with a domain qualified account-name and perform a lookup in the domain specific passwd file but this probably isn't necessary as it is not wise to open up your server to unnecssary access, especially command line access. Virtual domain support will be enhanced so that for each virtual domain a user account will be created (using the domain name) which has ownership of all the domain's files. This account would typically be the one then used to provide ftp and (possibly, but cautiously) ssh access. If additional ftp/telnet/ssh users are required they would need to be created using normal add_user commands on the virtual server, would appear in the satndard /etc/passwd, and could be manipulated using the sendmail /etc/aliases /etc/virtusertable files. Note that VSD virtual users cannot feature in the sendmail config files as sendmail has no concept of them. Tim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Lyn St George > Sent: 30 October 2001 12:45 > To: [EMAIL PROTECTED] > Subject: Re: Using freeVSD with default webserver > > > On Tue, 30 Oct 2001 10:50:10 -0000, Ben Kennish wrote: > > >Hi Johan, > > > >Yes, this is possible - although it requires a bit of extra work. > > > >Basically, it goes a little like this... > > > >The standalone daemons that are to run on the host server must be > >configured to only listen on the IP address(es) of the host server (so > >that they dont conflict with daemons running on the VSs.) > > > >For example, apache needs to be setup with a "Listen 11.22.33.44" line > >in httpd.conf (where 11.22.33.44 is the IP address of your host server) > > Do the same with sshd > > >Then there are the daemons run from (x)inetd.conf. I know that it must > >be possible because somehow we have telnet working on our host server > >AND our VSs (using the freeVSD 6.2-1 CDROM). > > I find that ftp, pop and smtp will work off xinetd, using the > standard VS entry, > even though they are working on the host and so do not need the > 'virtuald' > entry. I'm not at all sure why, but there is no problem. > > OTOH, the only reason I have users on the host, rather than putting them > all into a virtual server, is that I can't get ssh and ftp to work there. > > To explain that:- ssh and ftp work fine for the admin of a VS, > but when I add > 'virtual domains' to a VS, proftpd refuses to read the > 'virtualhost' entries > and ssh refuses to connect (yes, these users have 'login' enabled). > > >FreeVSD seems to work by using a program (/usr/sbin/virtuald) that (i > >assume) loads up the relevant daemon (in this case "in.telnetd") in the > >correct chrooted environment (whether that be the host server or a > >particular VS) when a connection request comes in (depending on what IP > >address the connection is to.) > > > >So, for standalone daemons, you need to setup their config files to > >ensure that it ONLY listens on the host servers IP address. For daemons > >mentionned in (x)inetd.conf, you'll need to wait for a response from > >someone who knows more about "virtuald" than me :) > > > >HTH, > > > > > >Ben Kennish > >[EMAIL PROTECTED] > >www.fubra.com > > > >----- Original Message ----- > >From: "Johan Pretorius" <[EMAIL PROTECTED]> > >To: "Freevsd-Support" <[EMAIL PROTECTED]> > >Sent: Tuesday, October 30, 2001 7:41 AM > >Subject: Using freeVSD with default webserver > > > > > >> I'm not quite sure how to phrase this, but let's try ... > >> > >> Will it be possible to install freeVSD on a server in such a way that > >the > >> "original" web server is still running? > >> > >> The scenario is as follows: we plan to lease a dedicated server, > >which will > >> have Plesk installed by default. One client will use the Plesk > >"portion", > >> whilst other clients will use virtual servers with the freeVSD > >supplied control > >> panel. > >> > >> Hope this makes sense! > >> > >> rgrds, > >> > >> Johan Pretorius > >> > >> http://host24.com > >> Your site. Every time. > > > > > >------------------------- The freeVSD Support List > -------------------------- > >Subscribe: > mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support > >Unsubscribe: > mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support > >Archives: http://freevsd.org/support/mail-archives/freevsd-support > >----------------------------------------------------------------- > ------------ > > > > > > ------------------------- The freeVSD Support List > -------------------------- > Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support > Unsubscribe: > mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support > Archives: http://freevsd.org/support/mail-archives/freevsd-support > ------------------------------------------------------------------ > ----------- ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
