Bryan Loniewski brylon@jla.rutgers.edu writes:
That was indeed the case! Thanks Pete. I needed to
./configure LDFLAGS= CPPFLAGS=
and all worked... using --with-lib-path and --with-include-path did not seem to work,
Are you saying you used --with-lib-path and --with-include-path with no arg? That's not how they're supposed to be used, if it works at all, it should just be a nop.
Anyway, if you know exactly what LDFLAGS and CPPFLAGS you want to use, setting them on the configure command line is the right thing to do.
If the developers would like to fix this I can email you the config.log of the 'working' and 'non-working' instances?
If you mail me the config.log, I can have a look at it. --with-*-path works for me, on Solaris.
On a side note, the 1.4.3 code does not do what I need it to (trusted host based auth only, when trying to run lshd with --no-password --no-publickey it core dumps),
Sorry, host based authentication is not supported. I think you're the first one who ever asks about that feature. I haven't really thought about it, but I don't want to ever recommend making the lsh client program setuid root. And it seems hard to support host based authentication without making something setuid. Server-only support could be done, I guess, but I'm not sure how useful that is.
I downloaded the latest 1.5.5 development code, and when 'make'ing ran into a snag, a patch is provided below.
Thanks, checked in now. /Niels