Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
01-06-2003, 09:12 AM
|
#1
|
Member
Registered: Nov 2000
Posts: 368
Rep: 
|
setting a trap
hi,
i am unsure if one of my servers has been hacked, as a precaution to see of the hacker comes back can i set a trap of some sort to tell me if someone is logging in?
if i can set a trap how would i go about it?
|
|
|
01-06-2003, 10:34 AM
|
#2
|
Member
Registered: Dec 2002
Location: In front of a computer
Distribution: UPS, DHL, FedEx
Posts: 466
Rep:
|
It depends where you suspect you've been hacked via, check all your log files everywhere for ip addresses or names that you dont recognize.
also try...
www.chkrootkit.org to see if they've left any back doors.
but setting a trap isn't going to do you any good if your software is still insecure, firstly upgrade your softwares to the latest versions so they're less likely to be hacked into, then try to fix things up otherwise they'll just come again and again.
|
|
|
01-07-2003, 01:39 PM
|
#3
|
Member
Registered: Dec 2002
Posts: 63
Rep:
|
Yes, check log files. A neat log watching tool is SWATCH ( http://packetstormsecurity.nl/UNIX/IDS/indexdate.shtml). You will need perl installed to run SWATCH. Once they are both installed you can configure SWATCH to look for both failed logon attempts as well as successful logon attempts. Since there shouldn't be too many people with the rights to logon to the server you will recognize a different name or IP if they have successfully logged on. Or you may find interesting patterns such as 2 failed attempts and a successful attempt all within 1 minute or something. This would be cause for concern. Configure SWATCH to send you an email in real time whenever something suspicious happens to your server. If you are running ssh disable root logons.
|
|
|
01-08-2003, 03:39 PM
|
#4
|
Moderator
Registered: May 2001
Posts: 29,417
|
I agree with niknah and cuss you should first check your reporting for anomalies, and then fix your current SW setup.
Please apply this rule before every other rule: if you can't trust a system for 100 percent, reformat+reinstall. I mean your best bet is to assess tru what means the compromise happened and what damage was done. Then decide to repair, restore a backup or reformat+reinstall on the basis of your knowledge + your assessment of the damage. Also don't forget to replace all security and authentication info after restore/reinstall.
Not to cramp your stylee, but I would never give you the advice to set up a trap or use a box as honeypot if you haven't got a clue about what damage has been done already and what the crackers intentions where/are. You may well be investing more time that you'll get (usefull) info out of it.
|
|
|
01-09-2003, 05:22 PM
|
#5
|
Member
Registered: Oct 2002
Posts: 41
Rep:
|
on the topic of honeypots....here is a site that has some very interesting info and gear regarding honeypots
http://www.project.honeynet.org/
Ed.
|
|
|
01-11-2003, 01:24 AM
|
#6
|
LQ Guru
Registered: Apr 2002
Location: Atlanta
Distribution: Gentoo
Posts: 1,280
Rep:
|
how do you disable root log-ons via ssh? and also, i see you guys mentioning reading logs, with a default install of 7.3, where would the logs be located or what are the filenames of said logs.
Last edited by Robert0380; 01-11-2003 at 01:27 AM.
|
|
|
01-11-2003, 06:45 AM
|
#7
|
Member
Registered: Dec 2002
Location: In front of a computer
Distribution: UPS, DHL, FedEx
Posts: 466
Rep:
|
edit /etc/ssh/sshd_config(or whereever sshd_config is) and change "PermitRootLogin no"
The logs should mostly be in /var/log/
|
|
|
All times are GMT -5. The time now is 07:57 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|