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-03-2007, 07:48 PM
|
#2
|
Senior Member
Registered: Jul 2003
Location: Silicon Valley, USA
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
|
Backup all your data and reinstall. There's no way to get an "untrusted" system back to "trusted" other than reinstalling the OS from scratch. Carefully examine all the data you backed up before restoring it to the new OS. In particular, check for any scripts, binary executables, or any other type of information that could be read through some kind of command interpreter. Once the system is compromised, every piece of information is suspect.
|
|
|
01-03-2007, 08:10 PM
|
#3
|
Moderator
Registered: May 2001
Posts: 29,415
|
While I too favour serving up ultimate worst-case scenario steps immediately I would suggest first finding out how the damage ocurred. Have a look at the Intruder Detection Checklist (CERT): http://www.cert.org/tech_tips/intrud...checklist.html.
|
|
|
01-05-2007, 05:35 AM
|
#4
|
Member
Registered: Jul 2003
Location: NY
Distribution: Slackware, Termux
Posts: 928
|
Quote:
Originally Posted by I_AM
|
That shows something changed, eg., something new was install, stripped, etc. It does not, in itself, mean you're done in.
Since the supposedly affected binaries are of the kernel modules tools, I'd say someone upgraded the module init tools and forgot about it (or stripped them.) There's also 3 kill's (in coreutils, util-linux, procps ) running around the linux community that I know of right now, depending on what rkhunter is using as it's criteria, it may be being confused by this.
The only thing the above shows for sure is you need to look around a bit more.
|
|
|
All times are GMT -5. The time now is 03:43 AM.
|
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
|
|