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 made a FS image with buildroot for x86_64, and I have loop mounted it and chrooted into it and added users to it as well as changing the root password. I tested it and made sure i could su all around to different users and all the passwords worked, and /etc/shadow and /etc/passwd exist and look fine to me.
Now I am using qemu to boot into the fs image using a kernel that I built, and it all works great except when I get the login prompt, nothing works. no matter what I type it always tells me the password is wrong. Its really annoying because I know that I have done this before successfully.
The buildroot version I used was a snapshot from 12/30/2011. Anybody have a similar issue and/or have any tips?
Hmm, I remember something similar with my distro. Are you sure the shell you use with that account is in /etc/shells? Can you login with "login" from root or is it just a console? There's also /etc/securetty in buildroot images IIRC, that can solve the problem with terminals.
Hmm, I remember something similar with my distro. Are you sure the shell you use with that account is in /etc/shells? Can you login with "login" from root or is it just a console? There's also /etc/securetty in buildroot images IIRC, that can solve the problem with terminals.
hmmm... /etc/shells doesn't seem to exist. But I made sure that the account uses ash as the shell, since that's the only one available. If the default shell was the problem, shouldn't it give me another error besides "login incorrect"? I already looked at /etc/securetty, I had to add tty0 to it to get this far since opening a getty on tty1 didn't seem to do anything.
Running "login" as root in the chroot environment doesn't seem to do anything at all, it just exits without switching users or asking for a login, no output at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.