SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok, I say im not a newbie, but i guess i am becuase i dont know whats going on...
here's the basis of it:
Slackware Login: root
/dev/tux/backup/login: Bad address
so yea. It wont let me logon
it wont prompt me for a password it just does that and goes right back to prompting me for a logon.
I have no other user accounts on this box, it is my server. I need it back up. Please help.
Hmmm...I would say to kill apache at start-up for now, but since you can't login...man, I don't know where to start. How about a linux boot disk password hacker...works on a SAM database, but not sure about your situation...let me see what I can find.
I'm not sure on this, but I think the directory /dev/tux is part of some root-kit. So I'm afraid you've been hacked. You might try booting from FIRE and do some testing on the system. Here's a link with some more information on the supposed root-kit http://seclists.org/lists/incidents/2002/May/0006.html .
Good luck with this.
I did some additional research and I've come up with this document with and in-depth description of the 'tuxkit' root-kit. It clearly states that the mere existence of the dir /dev/tux indicates that tuxkit has been installed. The cracker appears to have done a poor job given the fact that his/her root-kit has disrupted the login handling. I have no clue, however, on how to remove the kit and the binaries it has installed. It's not even clear wether the installation of the kit has succeeded. Like I said in my previous post you can use FIRE to do some forensics.