Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Mon May 14, 2012 11:40 am 
Offline
Newbie

Joined: Sat Apr 30, 2011 8:33 am
Posts: 3
Hi,
This is my second time that I'm reinstalling my server because of malicous attacks :D
So please can you give me tips on how to secure my linode.
I'll be using ubuntu 12.04 LTS.
Thank you


Top
   
 Post subject:
PostPosted: Mon May 14, 2012 12:18 pm 
Offline
Senior Member
User avatar

Joined: Sat Feb 25, 2012 4:44 pm
Posts: 71
Website: http://inhomeitsupport.com
First lock down ssh

make sure root is unable to log in

set up public keys and turn off password log ins this is where I would start


Top
   
PostPosted: Mon May 14, 2012 12:27 pm 
Offline
Senior Member
User avatar

Joined: Sat Feb 25, 2012 4:44 pm
Posts: 71
Website: http://inhomeitsupport.com
dyyyy wrote:
Hi,
This is my second time that I'm reinstalling my server because of malicous attacks :D
So please can you give me tips on how to secure my linode.
I'll be using ubuntu 12.04 LTS.
Thank you



How did they get in? How do you know that you were attacked?


Top
   
 Post subject:
PostPosted: Wed May 16, 2012 7:25 am 
Offline
Senior Newbie

Joined: Wed Mar 17, 2010 6:39 am
Posts: 8
Yes I'd be interested to know how you know too?


Top
   
 Post subject:
PostPosted: Wed May 16, 2012 7:36 am 
Offline
Junior Member

Joined: Tue Sep 25, 2007 3:04 pm
Posts: 27
-Don't use password authentication for SSH.
-Keep updated. If possible, get on mailing lists for applications you use (Apache, PHP). Follow various vulnerability databases. If you are unable to do this, run an update script every day.
-If you use a webserver there are many things to do to lock it down. Use something like the PHP Suhosin patch to limit the functions that can be used together. Lock down the combination of eval() and base64_decode() in a function in PHP. This will help guard against a LOT of issues.


Top
   
 Post subject:
PostPosted: Wed May 16, 2012 9:49 am 
Offline
Senior Member
User avatar

Joined: Sat Feb 25, 2012 4:44 pm
Posts: 71
Website: http://inhomeitsupport.com
A-KO wrote:
-Don't use password authentication for SSH.
-Keep updated. If possible, get on mailing lists for applications you use (Apache, PHP). Follow various vulnerability databases. If you are unable to do this, run an update script every day.
-If you use a webserver there are many things to do to lock it down. Use something like the PHP Suhosin patch to limit the functions that can be used together. Lock down the combination of eval() and base64_decode() in a function in PHP. This will help guard against a LOT of issues.


I run updates everyday and also I have a IDS (ossec) system running that emails me any issues in real time.

Just to add to your post


Top
   
 Post subject:
PostPosted: Wed May 16, 2012 10:15 am 
Offline
Senior Member
User avatar

Joined: Tue Mar 17, 2009 5:11 am
Posts: 129
Location: UK
Assuming your problem is SSH-related:

http://www.wolfpaw.co.uk/2012/03/securing-a-linux-vps/


Top
   
 Post subject:
PostPosted: Tue May 22, 2012 3:35 pm 
Offline
Senior Newbie

Joined: Wed Sep 08, 2010 5:13 pm
Posts: 14
Website: http://tds-solutions.net
AOL: sorressean
Location: Massachusetts
kyrunner wrote:
A-KO wrote:
-Don't use password authentication for SSH.
-Keep updated. If possible, get on mailing lists for applications you use (Apache, PHP). Follow various vulnerability databases. If you are unable to do this, run an update script every day.
-If you use a webserver there are many things to do to lock it down. Use something like the PHP Suhosin patch to limit the functions that can be used together. Lock down the combination of eval() and base64_decode() in a function in PHP. This will help guard against a LOT of issues.


I run updates everyday and also I have a IDS (ossec) system running that emails me any issues in real time.

Just to add to your post


How does that work out for you? I tried running snort as IDS as well as a port monitor, and ended up flooded with a ton of stuff. I don't have the knowledge to really set up a good ids setup and then to set up something else to monitor, so if I could get something like a daily logwatch email that tells me what I need, it'd be nice.

_________________
Take care,
Ty


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group