fioddor


Group: Members
Posts: 60
Joined: Aug. 2006 |
 |
Posted: Aug. 04 2007,21:53 |
 |
I've got the same question. I've got a frugal install.
In my case I just needed users with passwords to connect via ssh. The first answer was the passwd command. Then the remaining questions are
a) How to make the passwords persistant?
I've included /etc/shadow in the backup to make it persistant, but after rebooting the sshd doesn't recognise them. Though I can see the encoded passwords in /etc/shadow restored, typing them in the ssh client doesn't work. I get the connection rejected.
b) How to force the system to ask for them? After rebooting the machine, the system just loads without asking.
Note: When installing to hard disk the system creates and uses the passworded users. It requests the passwords to log in. How do we force the same effect in frugal installs?
|