Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Yes, it is possible to de-hash the passwords in /etc/shadow . There are programs (John the Ripper being the most-used on Unix) which can use dictionary and brute-force attacks against the hashes, and will eventually hit the right password.
Sorry, should have been a bit clearer. With exceptions of brutal force, database lookups etc, is there a way the user could use the encrypted password and send it to a ssh server for example? The password the user types in is encrypted with MD5 before sent to the ssh server isn't it? So a user could modify a SSH client potentially to send me string to the ssh server to get in as root?
SSH encrypts the whole stream and the password is passed down that encrypted channel, but it's not MD5 that's used (MD5 isn't an encryption algorithm, it's just a hash). The password (along with everything else) is decrypted by the SSH server before being used - most Linuxen use PAM to process authentication, so the password's passed to PAM in plaintext to be compared with the hash in /etc/shadow.
So no, having the MD5 hash on it's own won't let anyone in.