sixdiamants

Group: Members
Posts: 10
Joined: Mar. 2007 |
 |
Posted: Jan. 10 2008,22:21 |
 |
Another dirty trick is to add permanent users in /opt/bootlocal.sh and subsequently modify passwords. These users will live through subsequent reboots. Here's a sample of the code I added to bootlocal.sh
Code Sample | useradd -m -s /bin/bash utilisateurlambda chpasswd << EOF utilisateurlambda:nixbekannt dsl:charasjow root:beet EOF |
But now, you'll run into the next hurdle which is that the RSA keys aren't stored permanently either. I vaguely remember having seen some posts on the subject. As for me, I simply do:
Code Sample | rm .ssh/known_hosts | on the ssh client machine and then connect as user utilisateurlambda or dsl. Works a treat. Happy hunting...
-------------- ce qui se conçoit bien s'énonce clairement
|