If you get the error patterns-openSUSE-minimal_base-conflicts-12.1-25.21.1.x86_64 conflicts with python provided by python-2.7.2-7.1.3.x86_64, select the option deinstallation of patterns-openSUSE-minimal_base-conflicts-12.1-25.21.1.x86_64 and hit OK -- Try Again:
Hit Accept on the next screen...
... and finally OK:
Open /etc/postfix/master.cf...
vi /etc/postfix/master.cf
... and uncomment the following line:
[...]
tlsmgr unix - - n 1000? 1 tlsmgr
[...]
Create the following symlink:
ln -s /usr/lib64/dovecot/modules /usr/lib/dovecot
Start MySQL, Postfix, and Dovecot and enable the services to be started at boot time.
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none): <-- ENTER
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.
Set root password? [Y/n]<-- Y New password:<-- yourrootsqlpassword Re-enter new password:<-- yourrootsqlpassword Password updated successfully!
Reloading privilege tables..
... Success!
By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n]<-- Y ... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n]<-- Y ... Success!
By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n]<-- Y - Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n]<-- Y ... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MySQL
installation should now be secure.
Thanks for using MySQL!
server1:~ #
Now your MySQL setup should be secured.
9 Amavisd-new, Spamassassin And Clamav
Install Amavisd-new, Spamassassin and Clamav antivirus. Run
OpenSUSE 12.1 has a /run directory for storing runtime data. /run is now a tmpfs, and /var/run is now bind mounted to /run from tmpfs, and hence emptied on reboot.
This means that after a reboot, the directory /var/run/clamav that we have just created will not exist anymore, and therefore clamd will fail to start. Therefore we create the file /etc/tmpfiles.d/clamav.conf now that will create this directory at system startup (see http://0pointer.de/public/systemd-man/tmpfiles.d.html for more details):
vi /etc/tmpfiles.d/clamav.conf
D /var/run/clamav 0755 root root -
Before we start amavisd and clamd, we must edit the /etc/init.d/amavis init script - I wasn't able to reliably start, stop and restart amavisd with the default init script:
vi /etc/init.d/amavis
Comment out the following lines in the start and stop section:
[...]
start)
# ZMI 20100428 check for stale pid file
#if test -f $AMAVIS_PID ; then
# checkproc -p $AMAVIS_PID amavisd
# if test $? -ge 1 ; then
# # pid file is stale, remove it
# echo -n "(stale amavisd pid file $AMAVIS_PID found, removing. Did amavisd crash?)"
# rm -f $AMAVIS_PID
# fi
#fi
echo -n "Starting virus-scanner (amavisd-new): "
$AMAVISD_BIN start
#if ! checkproc amavisd; then
# rc_failed 7
#fi
rc_status -v
#if [ "$AMAVIS_SENDMAIL_MILTER" == "yes" ]; then
# rc_reset
# echo -n "Starting amavis-milter:"
# startproc -u vscan $AMAVIS_MILTER_BIN -p $AMAVIS_MILTER_SOCK > /dev/null 2>&1
# rc_status -v
#fi
;;
stop)
echo -n "Shutting down virus-scanner (amavisd-new): "
#if checkproc amavisd; then
# rc_reset
$AMAVISD_BIN stop
#else
# rc_reset
#fi
rc_status -v
#if [ "$AMAVIS_SENDMAIL_MILTER" == "yes" ]; then
# rc_reset
# echo -n "Shutting down amavis-milter: "
# killproc -TERM $AMAVIS_MILTER_BIN
# rc_status -v
#fi
;;
[...]
Because we have changed the init script, we must run
Next we build the mod_ruby Apache module (it is not available as an OpenSUSE 12.1 package, therefore we have to build it ourselves):
yast2 -i apache2-devel ruby ruby-devel
cd /tmp
wget http://modruby.net/archive/mod_ruby-1.3.0.tar.gz
tar zxvf mod_ruby-1.3.0.tar.gz
cd mod_ruby-1.3.0/
./configure.rb --with-apr-includes=/usr/include/apr-1
make
make install
a2enmod ruby
To add Python support, run:
yast2 -i apache2-mod_python
a2enmod python
Next we install phpMyAdmin:
yast2 -i phpMyAdmin
To make sure that we can access phpMyAdmin from all websites created through ISPConfig later on by using /phpmyadmin (e.g. http://www.example.com/phpmyadmin) and /phpMyAdmin (e.g. http://www.example.com/phpMyAdmin), open /etc/apache2/conf.d/phpMyAdmin.conf...
vi /etc/apache2/conf.d/phpMyAdmin.conf
... and add the following two aliases right at the beginning:
Alias /phpMyAdmin /srv/www/htdocs/phpMyAdmin
Alias /phpmyadmin /srv/www/htdocs/phpMyAdmin
[...]
Please do not use the comment function to ask for help! If you need help, please use our forum. Comments will be published after administrator approval.
Recent comments
1 day 5 hours ago
1 day 13 hours ago
1 day 16 hours ago
1 day 18 hours ago
1 day 19 hours ago
1 day 21 hours ago
1 day 22 hours ago
1 day 23 hours ago
2 days 15 hours ago
2 days 16 hours ago