On Fri, Jan 22, 1999 at 12:01:40 -0600, Gordon Matzigkeit wrote:
> So, I gutted all the configure code, and replaced it with a runtime
> option: --ssh1-fallback=SSHD. There is no reason that I can see to
> hardcode the location of a working sshd1 into lshd, even as a default. If
> people were smart enough to run sshd, they should be able to add a flag to
> lshd's startup script, and figure out from the log that they need a
> version that supports -V.
>
> --ssh1-fallback flag isn't the default, so it is possible to disable
> ssh1 support (for whatever reason) without recompiling.
On Fri, Jan 22, 1999 at 20:00:36 +0100, Niels M�ller wrote:
> I think it would make sense to have a configure time option --with-sshd1,
> to make it possible to (i) disable the callback code completely, and (ii)
> specify a default path for the sshd1 program. I agree that it seems
> unnecessary to try to figure out automatically whether or not a suitable
> sshd1 program is available.
I agree that it is not necessary. But i don't think it should just be gutted
away. IMO it would be nice if the configure script still did the test, but
warn about a too old SSH1 rather than abort.
Ray
--
Cyberspace, a final frontier. These are the voyages of my messages,
on a lightspeed mission to explore strange new systems and to boldly go
where no data has gone before.
