Keresztfalvi Gabor Agoston <[EMAIL PROTECTED]> writes:
> It works for me on my Linux box, but I realized, that for example on AIX this
> wouldn't work, because in /etc/passwd there is '!' (and not 'x') instead of
> the password... This needs some workaround. Possibly other systems use other
> chars instead of the password...
Is there any standard or canonical documentation on how shadow
passwords should work?
> BTW 1.: On some systems there is not any crypt.h. It should be checked for in
> configure.
I know. Should be fixed.
> BTW 2.: I still can't get lsh to work because of that EPIPE. I tried it on
> SuSE 5.3 Linux with kernel 2.0.35(SuSE patched) and 2.1.130, with libc5.4.46
> on two different hardware (but I think this is not important (P133 and
> AMDK5PR100, both with HX motherboard and 64MB RAM different networkcards)).
> C compiler is: gcc version 2.7.2.1
>From your earlier bug report, it seems that it is the child process
which dies of EPIPE, when attempting to write to its stdout. Is that
correct? I think the first target to look closer at is the use of
shutdown(). Either lsh, your shutdown(), or the code to workaround the
shutdown() bug in linux-2.0.33, may be broken.
> Please, who has ever compiled and tried lsh, send me a mail with your HW/SW
> config, lsh version and results of running, because I'd like to make a
> summary, where lsh worked, and where didn't. I hope this will help us to solve
> that EPIPE.
I'm currently using a SparcStation 5 running sparc-linux, redhat-5.1,
kernel 2.0.33.
> P.s.: Please forget Agoston from my name, because it's my second first name :)
> and I don't use it. Indeed my name is still long enough without that. :)
> Use my nickname: Keresztg
I'll try to remember that.
/Niels
