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.
I have a mail server that authenticates from the user's shell password listed in /etc/shadow (encrypted) and then my web server has some html documents that are password protected using 'htpasswd'. I tried to copy the encrypted password from /etc/shadow to my web servers htpasswd/passwd file. When I did, it would not let the user in to view the html pages because it did not like their password I copied over from the mail server. Can someone tell me why this does not work? Is the encryption a different algorithm for shell than htpasswd?
The encryption is a different algorithm, but also using the shell password as a web password isn't something you want to do from a security perspective. The shell is protected by a time delay between attempted logins that is gradually increased with each attempt. The HTTP server does not do this. Therefore, a cracker can hit your web server hundreds of times a second (more or less depending on how you have your server configured), drastically reducing the time it would take to perform a brute force attack on your password.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.