Changing password authentication from DES to SHA 512
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.
Changing password authentication from DES to SHA 512
I have an embedded ELDK controller which is currently operating on the basis of DES password authentication. None of the /etc/shadow entries have a password field which is prefixed with ${digit}$.
Purely for improved security and the need to integrate with some third-party software, I need to change the authentication type to SHA-512, and I am roughly aware of what needs modifying in login.defs to do that.
However, I'm concerned as to what will happen when I reboot after the change. Do existing password entries get left intact as they are ?
If so, I'm happy with that, because there aren't that many users that would need the password re-encrypting. And it would probably answer the other concern I have about root access, i.e. presumably, I won't lose the ability to log back in with my existing root user ?
@Habitual Thanks for the welcome. I'm normally a Java developer so this project is a bit out of my normal comfort zone! Can I take you up on your reply ? My primary connection to the controller is putty via serial to the controller's RS232 'debug' port. The controller also runs an ssh server which I can putty into over IP. However, I am assuming your paradigm of 'test, disconnect, reconnect' implies a controller reboot after modification of login.defs and so, surely, I will lose the second connection at that point ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.