We have webmin working in the virtuals with no problems...
We added webmin to the skel under /usr/packages/webmin
Right now we do a manual setup for each virtual that needs webmin (we are
using /etc/webmin for the configuration files, but any directory own by
root.root would do).
Once we have a few things a little better (in webmin), I think we will
include the building of /etc/webmin/ and it's files in vsd-vsbatch.pl
A few considerations:
1.- don't use version 0.85... it have a small security hole... it writes
some files under /tmp with the wrong permissions.
2.- remember to bind webmin to the IP address of your vs! (if not, it will
be listening in all IP's!!!)... If you do this, you could use the same
ports for all the webmins in all vs's
3.- if you go the same route we went (having all of the .pl
files... produced when you untar webmin...) under your skel... remember
that in each VS those files are hard-linked... any modification to one of
those files will be reflected in every vs.! (I made a "booboo" in that
regard... installing webmin in one of the VS I defined a version of Perl
that only that vs has!... webmin stopped working in all other vs's)
4.- if you add a module... you need to do it from a working VS, and if
you decide that it's something you want to have in all your vs (present
and future), you need to
cp -lr /home/vs/virtualname/usr/packages/webmin/newmodule \
/home/skel/usr/packages/webmin/
and also added to every VS (either with a cp -lr or updating via vsd, both
are ugly :( (I use cp -lr). Also you'll need to manually add the use of
that module in every vs for the appropriate webmin user.
5.- Once you decide which modules you don't want (or need), you should
remove those from /home/skel/usr/packages/webmin/
6.- the module "custom commands" (under others), is a handy tool to create
small scripts (shell scripts or Perl) to manipulate things like setrights
or....
8.- right now I offer my clients the modules for sendmail, apache, mysql,
change password, add users and groups, and of course they do not have
rights for every possible operation in each module (except mysql, where
the only disallowed operation is modify module configuration).
7.- I hope that next week I will have the time to start modifying addusers
and groups and other modules in such a way that the VS's admin will be
able to create a new user and give that user the appropriate rights (right
now I have a simple script under "custom commands", but it is inconvenient
for my clients. (of course, I hope.. but... I have tons of things to be
done after taking two summer classes... and for the Perl programming itself
my partner needs to help me ;)
also... within a few weeks I will try to have a demo working someplace (to
show prospective clients... but could be use to show anybody interested ;)
In as much as security, I do not think that webmin is more insecure that
the webadmin offered by Idaya. If you install ssh, and the Perl modules,
you could run webmin in such a way that your clients will be forced to use
https (a good idea).
Cheers!
Marcos
------------------------- 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
-----------------------------------------------------------------------------
