I am having to delete a client account due to non-payment of the service provided. He has threatened to "hack" into my servers and destroy them if I do. Now as a security precaution, I would like to know, is CPANEL secure enough to keep my server safe and outa harms way?
Just ignore him, it's just blackmail, I am sure he doesn't even know the first thing about hacking Just make sure you have the most up-to-date version of CPanel installed on your machine, it is currently 4.9-Somthing
Chris Adams - CEO - Rochen Ltd. - chris (at) rochen (dot) com
Now offering both US & UK premiumbusiness hosting, reseller hosting and managed virtualized services. rochen.com | rochen.co.uk | blog.rochen.com | forums.rochen.com | Twitter: @rochenhost
I think the question is, "is my server secure enough". Cpanel has nothing to do with security, but it does help tighten things up by upgrading old versions of software. Its ultimately up to you as a system admin to secure your box. Ensure that holes are patched, and firewall is active, etc. If you have the users IP, you can perhaps add that, or its range to your firewall. Its not fool proof but its a start.
Keep in mind that Cpanel is not a system administration tool. Its a control panel. Its a tool to help make your life as a web host a little easier.. not any more secure!
hackstar.com . i dont even think hes a hacker..probably a script kiddie. i even believe this hackstar guy is a scam! look at his site..you have to send him your credit card dtails or money in the mail???
Hackstar.com is home to many tutorials written by Hackstar Publications from major hacking projects to bypassing "No Right-Click" scripts.
bypassing No Right click scripts?..haha..just ignore him..most he can do is probably spam you with some bulk mail programs.
- verify your interchange is disabled (bug/exploit still open afaik),
- that you've manually updated your openssh (burstnet claims they have the fix in their version, but i had 2 boxes hacked from the openssh exploits, and they were running automatic updates).
- Make sure your apache + php is up to date (you have to manually do the buildapache).
- Add the little mofo's ip range to your /etc/hosts.deny