Since we're discussing secure ways to access the server. Another method that I use is Webmin. I use it mainly for quick checks of Postfix's log for immediate troublshooting. However, Webmin is much more capable than that.
The only cavaet is to invoke CPAN and install the NET::SSLeay module. This will permit an encrypted connection to Webmin's web server.
Take your time, we are not in a hurry. To help you make choices there is another famous quote: "Leave the gun and take the cannoli"
jstubbs 20 Oct 2006
THIS ARTICLE IS FOR REVIEW ONLY.
Please review and advise. With any comments, I'll clean up the text and any errors.
Before installing Webmin, we need to add Perl's Net::SSLeay module to your Perl installation. If you have experience with Perl, you know what to do. If not, we need to invoke CPAN for the first time and set it's configuration parameters. You can accept almost all the default answers when running CPAN's configuration script. There are two questions, that need your consideration. The first will be the mirrors that CPAN checks for modules. Please choose the proper continent/country. The script will then let you choose the mirrors for your locale. I choose a lot of them, I would advise you to do the same. The second will decide whether or not to build dependencies. I always choose to let CPAN "follow" (build) all neccessary dependencies. I don't do a lot of Perl programming, so I am unlikely to run into module conflicts.
To get started, open a Terminal window and launch CPAN with:
sudo perl -MCPAN -e shell
The configuration script will then launch, just accept the default answers, with the above exceptions noted. After configuration has ended, you will be at the cpan prompt.
Here you will need to enter:
cpan> install Net::SSLeay
CPAN will then update its module database and then download and install Net::SSLeay module. After the build stage it will move on to testing the module and will connect to several sites to test the security of the module. I have never run into problems installing this module. After the module is installed, just:
cpan> exit
You will be back at the shell prompt.
Now we are ready to install Webmin.
You can download and read the installation instructions from here
Install is pretty straight forward but review the instructions for the unix install.
After downloading, in the Terminal
cd /path/to/the/downloaded/FILE
tar zxf webmin-1.300.tar.gz
cd webmin-1.300
sudo ./setup.sh /usr/local/webmin
When the setup script runs, it will ask a short series of questions.
Accept the default answers for:
A) webin configuration directory
B) Webmin log directory
C) path to perl
D) OS type
The answers you need to supply are:
E) SSL web server PORT - default is 10000, too many numbers for me, I usually pick something in the 80?? range.
F) login name - choose one to your liking and write it down or memorize it.
G) password - same as #F
H) web server hostname - usually picks the correct name from hostname, but double check it.
I) Use SSL - choose yes
J) Start Webmin at boot - choose yes
After this, the script will churn thru its steps, and will inform you when it completes.
Test it out by launching a browser, and try this web page:
You should be presented with the login page. ENJOY.
Currently, you can access the Postfix mail logs and configuration files & the mysql server. Over the weekend, I going to try to reconfigure the Apache module to control the Apache2 webserver. Sorry, no module for Courier.
To check your sever from elsewhere, don't forgot to modify the firewall and open the necessary port.
Help support Webmin for OS X by reporting the OS to the developers from within Webmin.
Jeff, thanks I wil try it out this weekend and will let you know how it works.
jstubbs 22 Oct 2006
jstubbs Escribió:
Over the weekend, I going to try to reconfigure the Apache module to control the Apache2 webserver.
Getting Webmin to realize that I was using Apache2 was really easy. In the Webmin's servers tab, just choose the Apache icon and then, click on the modules config link. It was just a matter to changing the System Configuration fields from the default Apple values to your Apache2 install directory values. I installed Apache2 into /usr/local/apache2. Richard's default install was slightly different if I remember, (I'm just too lazy to pop over to the blog and confirm). On saving the module, the Apache version had changed to 2.2.3 and showed my virtual servers. Stopped and started the server fine.
22 Sep 2006
The only cavaet is to invoke CPAN and install the NET::SSLeay module. This will permit an encrypted connection to Webmin's web server.
15 Oct 2006
16 Oct 2006
16 Oct 2006
20 Oct 2006
Please review and advise. With any comments, I'll clean up the text and any errors.
Before installing Webmin, we need to add Perl's Net::SSLeay module to your Perl installation. If you have experience with Perl, you know what to do. If not, we need to invoke CPAN for the first time and set it's configuration parameters. You can accept almost all the default answers when running CPAN's configuration script. There are two questions, that need your consideration. The first will be the mirrors that CPAN checks for modules. Please choose the proper continent/country. The script will then let you choose the mirrors for your locale. I choose a lot of them, I would advise you to do the same. The second will decide whether or not to build dependencies. I always choose to let CPAN "follow" (build) all neccessary dependencies. I don't do a lot of Perl programming, so I am unlikely to run into module conflicts.
To get started, open a Terminal window and launch CPAN with:
sudo perl -MCPAN -e shellThe configuration script will then launch, just accept the default answers, with the above exceptions noted. After configuration has ended, you will be at the cpan prompt.
Here you will need to enter:
cpan> install Net::SSLeayCPAN will then update its module database and then download and install Net::SSLeay module. After the build stage it will move on to testing the module and will connect to several sites to test the security of the module. I have never run into problems installing this module. After the module is installed, just:
cpan> exitYou will be back at the shell prompt.
Now we are ready to install Webmin.
You can download and read the installation instructions from here
Install is pretty straight forward but review the instructions for the unix install.
After downloading, in the Terminal
cd /path/to/the/downloaded/FILEtar zxf webmin-1.300.tar.gz
cd webmin-1.300
sudo ./setup.sh /usr/local/webmin
When the setup script runs, it will ask a short series of questions.
Accept the default answers for:
A) webin configuration directory
B) Webmin log directory
C) path to perl
D) OS type
The answers you need to supply are:
E) SSL web server PORT - default is 10000, too many numbers for me, I usually pick something in the 80?? range.
F) login name - choose one to your liking and write it down or memorize it.
G) password - same as #F
H) web server hostname - usually picks the correct name from hostname, but double check it.
I) Use SSL - choose yes
J) Start Webmin at boot - choose yes
After this, the script will churn thru its steps, and will inform you when it completes.
Test it out by launching a browser, and try this web page:
https://your.server.name:PORT/
You should be presented with the login page. ENJOY.
Currently, you can access the Postfix mail logs and configuration files & the mysql server. Over the weekend, I going to try to reconfigure the Apache module to control the Apache2 webserver. Sorry, no module for Courier.
To check your sever from elsewhere, don't forgot to modify the firewall and open the necessary port.
Help support Webmin for OS X by reporting the OS to the developers from within Webmin.
20 Oct 2006
22 Oct 2006
jstubbs Escribió:
Getting Webmin to realize that I was using Apache2 was really easy. In the Webmin's servers tab, just choose the Apache icon and then, click on the modules config link. It was just a matter to changing the System Configuration fields from the default Apple values to your Apache2 install directory values. I installed Apache2 into /usr/local/apache2. Richard's default install was slightly different if I remember, (I'm just too lazy to pop over to the blog and confirm). On saving the module, the Apache version had changed to 2.2.3 and showed my virtual servers. Stopped and started the server fine.