Robert Schwebel <[EMAIL PROTECTED]> writes:
> I tried that but it doesn't work. I have a second user on the machine
> which has no password (login via telnet does work), and I also cannot
> login via lsh to his account.
lshd is a little paranoid, and it doesn't allow logins to accounts
with no passwd-field in the paswd database (an empty password, as
generated by crypt("salt", ""), should work, though). See the comment
before the do_lookup_user function in unix_user.c for the rules lshd
use when reading the user database.
> It also doesn't matter if I use the openssh or the lsh client.
That makes sense, as it's a server configuration/policy issue.
> Even changing to a "real" password does not help... coud this be caused
> due to wrongly set permissions of some of the configuration files?
An ordinary user with a real password is the normal case, and that
should certainly work. How is your system set up? Do you have a plain
/etc/passwd file with encrypted passwords in, or do you use shadow
passwords? Is PAM involved in any way?
/Niels
_______________________________________________
lsh-bugs mailing list
[EMAIL PROTECTED]
http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
