Archive for the ‘Web Servers Security’ Category:
How to secure SSH in your server ?
1) Set a very strong password, keep it in your mind but dont write in somewhere.
2) Disable direct root login
emacs /etc/ssh/sshd_config
Search for
More »
why sites suddenly stopped working in dedicated/virtual private servers
VeriSign has made some changes recently which are applied since March 1, 2010. You can read detail by clicking here
How do I fix it?
You need to log in to your control panel and modify the affected domain name’s zone file, using the table below as an example. More »
ip_conntrack table is full and dropping packets
Last day one of our server had an attack, attack was not so big but still server was unresponsive because of this. After some research I found that this is because of iptables which are being load while handling so much traffic. Then I found a good article on the same issue which you can read by clicking below linking here.
Installing & configuring shorewall firewall in Ubuntu/Debian
Shore line firewall known as “Shorewall”, it is a very high level firewall and very easy to install and ocnfigure
How to install :-
sudo apt-get install shorewall
Browser security handbook by Google
Browser security handbook is released by Google, and google has described it as “a comprehensive, 60-page document meant to provide Web application developers and information security researchers with a one-stop reference to several hundred key security properties and sometimes counterintuitive quirks in contemporary Web browsers.”
Book is written by “Michal Zalewski”, who is very a famous researcher by Google. The introduction of book describes that there are very important differences between browsers and lists market share data of browsers on which the document is based. It is Net Applications data, rather than straight Google data, which the company does not release.
five important tips to secure your wordpress blog
One of the utmost concerns among those of us running web applications on the web that are always available should be security. Whether or not you have personal data in your blog is immaterial. A compromised site can be used as a jumping off point for many other types of malicious behavior. Very few hackers will overlook a free lunch no matter how insignificant you may feel like your blog might be. An easy target is an easy target and although your site might be obscure, like anything else on the web, that isn’t protection against intrusion. Proactive security is the only thing that will keep your content safe. This becomes especially important if you’re using WordPress for commercial purposes as a hacked site that generates a lot of spam or otherwise hostile activity is going to be delisted from the major search engines and possibly included on spam blacklists. Here a are a few tips for getting started and some plugins that can help ease the burden a little.
1. Keep your version of WordPress current. Whenever you see the notification that there is a new version of WordPress available it is your best interest to download and install it. Keeping your software current is a minimum requirement for security. Unlike most other things in life, software does not age gracefully and you can save yourself a lot of hassle by staying current with releases. WordPress Instant Upgrade can help out with that if you’ve not done large numbers of modifications of the original files. You can find out which version of WordPress you’re currently using by looking near the bottom of your admin page. It should say something like Version 2.x.x on the bottom most line. If it says something like Version 1.x then you need to take action immediately.
2. Make backups. Whether you do this manually with an FTP client and the output of PHPMyAdmin for database tables or with an automated solution like the WP-DB-Backup plugin. Try to do them weekly if possible and keep a copy on your computer if possible. The WP-DB-Backup plugin gives the option to do both of those as well as deliver the backups to an email address. Offsite is always best but your home or work computer is better than no backup at all. You could always grab a Gmail address specifically for this plugin which shouldn’t give you trouble with capacity given the large quotas that Gmail gives us to work with.
How to add new RBLs to cpanel Exim
More then a year ago, cPanel added a future to the Exim Configuration Editor for everyone to easily select from two RBLs (spamhaus.org and spamcop.net) that can be used to filter most of the SPAM that a server receives. While this has been great for most of us (enabling a RBL is a simple as selecting a check box in WHM and pressing the Save button), there are a few admins that would have liked to add additional RBLs to the list that Exim uses to filter SPAM emails. RBLs like dnsbl.njabl.org, list.dsbl.org, dul.dnsbl.sorbs.net, etc. are all considered useful by many, but not included by default.
The question is how can such a RBL be added to Exim ?
Well it’s not that hard !
First you will have to login to your server using ssh.
After a successful login:
- Change directory to /usr/local/cpanel/etc/exim/acls/ACL_RBL_BLOCK
More »
How to catch spammer or Scammer in Cpanel server?
1. Open exim.conf
pico /etc/exim.conf
2) Find this;
Ctrl + W: hostlist auth_relay_hosts = *
#########################
Runtime configuration file for Exim #
#########################
3) After hostlist auth_relay_hosts = *
Installing BFD (Brute Force Detection)
2) Download BFD
wget
http://www.rfxnetworks.com/downloads/bfd-current.tar.gz
3) Unpackage the download
SSH login message
(By default I have this set only to the root user and no shared accounts. but it’s up to you what you do…)
Top create a login message login via root with your favourite SSH client (PuTTY!!)
and type this
pico /etc/motd