From: Seiler Thomas (seiler.thomas_at_gmx.net)
Date: Tue 09 Apr 2002 - 12:35:40 BST
Jon Bendtsen wrote:
> CÚdric Veilleux wrote:
> > I have not a lot of experience with vservers, but simply from reading
> > documentation, I've found a few important drawbacks:
> > One IP address per vserver:
> > An important drawback that will make a good part of your clients
whine. It is
> > only possible to have 1 IP per vserver. So it is not possible to use IP
> > virtual hosts in apache (required for SSL, etc..)
> "A vserver may operate with 0.0.0.0 as its IPROOT. This means the
> vserver is allowed to use any IP it wants..."
Isn't this a little bit contradictory ?You have this very nice vserver
gives you absolute isolation between vservers, imagine Sandboxes to try
software, absolute isolation for virtual hosting clients, etc...
But as soon as a vserver needs more that one IP (common situation in hosting
the only solution consists in setting IPROOT to 0.0.0.0 allowing the vserver
to mess around
and bind to any IP's it isn't supposed to. Security Sandbox gone. Isolation
clients gone, and it's only a question of time before they will get into
each other's hair ...
So the only real souloution to this consists in some way to allow assignment
IP's per vserver. I saw there was once a patch for mutliple IPs per vserver,
maintanced anymore. Would't that be a great starting point for a new
multiple IP patch ?
So does anybody know where i can find the old patch ?
After all, this would be a very nice feature for hosting environments and I
think there *IS*
enough demand. Think for example of multiple SSL hosts within a vserver, of
for Webserver and MailServer, etc...