Tag: Linux
-
AWS, WordPress, Bitnami, and Ansible – A Journey
In The Beginning… I’ve been running a number of WordPress sites at AWS, and using the Bitnami AMIs to do so. They make it super easy, just fire up an instance of the AMI, and boom you have a full WordPress environment up and running, with Apache, WordPress, and a database. When The Palace…
-
Automated ClamAV Virus Scanning
Automating Linux Anti-Virus Using ClamAV and Cron Thankfully Linux isn’t a platform which has a significant problem with Viruses, however it is always better to be safe than sorry. Luckily ClamAV is an excellent free anti-virus solution for Linux servers. However, at least on RedHat Enterprise 5 (RHEL5) the default install doesn’t offer any automated…
-
Setting Up SPF, SenderId, Domain Keys, and DKIM
If you run a mail server, and if you hate spam, you should setup your mail server to make use of all the best anti-spam tools available. There are two sides to spam, sending and receiving. On the receiving side, you have things like blacklists, spamassassin, bayesian filtering, and lots more. I’ll probably cover this…
-
Why I love Debian (and PostgreSQL)
I woke up this morning, got online through my new UMTS/HSPDA modem, and discovered that one of my servers had a load average of 239+ Not the best way to start the day. Turns out an rsync backup job between two servers had gone nuts and was spinning them up through the roof. A couple…
-
Using IPTables to Prevent SSH Brute Force Attacks
If you have a server with a world facing ssh server, you’ve probably seen brute force attacks in your logs. Some machine starts hammering your ssh server, trying all sorts of logins (staff, root, a, admin, etc…) over and over and over again. This is bad on a lot of fronts. I use two simple…
-
How to identify the process listening on a port
This is mostly for own use, but: If you’ve ever had a server which netstat showed was listening on one or more ports you weren’t expecting, you can use this command to find out which process is listening there: fuser -vn tcp 4444 Which in this case happens to be owned by JBoss, and not…