Linux - SecurityThis 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.
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.
keep in mind that , unless it was a very stupid hacker, they haven't hacked you from there own address. there may be many innocent addresses between your box and the hacker.
Also this should prompt you to make your server more secure. Try browsing these forums with lots of good information. You might want to disconnect it for now to be safe until you know it is safe to bring back up on the net.
Originally posted by david_ross "last" will show logins
"lastb" if enabled shows bad logins
"more /etc/httpd/logs/access_log" will show web connections
Next to the fact they might be using intermediate servers they might have zapped shell and login history as well. Chkrootkit can find zap AFAIK, but can't find deleted data. If you really want to know what traces they left after they shredded stuff you'll have to dd an image of the disks, partitions and run TCT.
Mind you, it ain't a trivial task so I'd only recommend it for situations where it is crucial to have the knowledge, it'll take lots of time and you have to know how to construct the timeline and interprete the pieces to build the puzzle. Also chances of reconstructing get slimmer the longer the system remains active (disk writes).
Btw, would you mind posting your general network layout (if any), what daemons you where running, if you where up2date and if you got *anything* out of *any* logfiles?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.