Direkt zum Hauptbereich

Posts

Posts mit dem Label "server" werden angezeigt.

Almost perfect mail server: postfix - dovecot - postgresql -- with virtual mail boxes and SSL

Its a long time ago I had enough time to set up my mail server, so I will summarize my steps, or better: my problems: [on debian 7] install postfix install postfixadmin install postgresql make them work together as they all should use virtual users install dovecot and make it the default SSL handler for postfix, main.cf master.cf etc. Well, this is bull because its of no help to anyone, the devil resides in the details: postfixadmin sets up the database postfix should use queries for to look for mails in the database, so virtual_mailboxes etc have to be set up dovecot should be the MDA for the MTA postfix dovecot and postfixadmin should use a simple and same encryption, because both look into the database; is this step is done (and it took me a while, CRAM-MD5?) you can set up mailboxes via the web interface postfixadmin

Putting phpPgAdmin behind SSL virtualhost and securing it a bit more

This could be a huge post, but I am cutting it short: configure pg_hba.conf right, e.g. set host stuff to password md5 try to connect to your database locally to test it, e.g. psql -U user "psql -U user dbname -W" and type in the password install phppgadmin, e.g. on debian I could not find a /etc/phppgadmin/apache.conf but a /etc/apache2/conf.d/phppgadmin your apache2 should be able to serve SSL, otherwise look a my post from yesterday: SSL virtualhost after you setup a SSH connection through rsa keys and always redirect to it in order to serve multiple site using SSL you should change to *:443 instead of _default_ also you have to tell /etc/apache2/ports.conf to use NameVirtualhost when listening on 443; otherwise apache will tell you about conflicting virtualhosts. apache2: now its time to copy the content of conf.d/phppgadmin into a sites-available file and dont forget to delete the alias line and adjust names and folders. From now on I followed these steps: Step...

etherpad lite user basic authentication hussle - bloody JSON files

After migrating my server from one account to another, basically setting it up again, I ran into some problems with my etherpad lite installation. Since my first post on this I wanted to add some more users for more control whose group is accessing what pad. But there was always something wrong! My conclusions: use "service etherpad-lite restart" instead of the /admin restart button make sure that apache is running or restart it often enough change the bloody JSON file trough the /admin interface since its telling you about corrupt syntax Last point on the list was my major problem for I forgot to put down some more blanks in order to have the JSON hierarchy. After that was sorted my basic authentication ALMOST worked: dont use "requiresession = true" for it messes up some stuff somehow Now my installation works like a charm with my postgresql database.

webmin port problems - firefox port protection

I had some trouble setting up my webmin panel, and one thing was firefox with its port protection. Just do the following: about:config as url add string value: network.security.ports.banned.override fill it with a comma seperated list, e.g. just 10000 for webmin And of course the ports must be open or listend at on the server, test this on the server with:   netstat -an | grep :10000 And locally you can also do a nmap your.server.com

debian 6 vserver - a new installation due to centOS update problem - my steps

My centOS vserver broke down after a "yum update" and even the centOS community forum could not give an answer within 24h. In my books that is poor for the almighty and stable centOS. Bare in mind that I am just a normal user of linux, no professional and definitely no expert when it comes to server, but I can read, try and share my findings: debian 6 installation steps via ssh secure your server: adduser foobar for security purposes  change /etc/sshd/sshd_conf to PermitRootLogin no now you can login as foobar and change to root via su - visudo for sudo command permissions and put this at the bottom: foobar   ALL=(ALL) ALL change hostname change hostname in /etc/hostname and in /etc/hosts reboot login via rsa key rather than password locally do ssh-keygen ssh-copy-id -i foobar@hostname... ssh now works without passwords but with keys (for easy deployment) install ruby and rails via rvm login as root always good to have: sudo apt-get install...

ssh remote rsa key login (without password)

After changing my system to manjaro I had to recover some settings, and sadly had to do some things again, e.g. my ssh login via rsa keys. After doing it manually I saw this 3 step answer on some message board: ssh-keygen Press Enter key till you get the prompt ssh-copy-id -i root@ip_address (It will once ask for the password of the host system) ssh root@ip_address Now you should be able to login without any password One thing I had to change: chmod 700 .ssh on the remote machine, and then it worked like a charme.