Re: OpenSSH 4.7: call for testing.

On Fri, 17 Aug 2007, Darren Tucker wrote:
> > There was no configure script in the code that I obtained from
> > "cvs -d anoncvs@anoncvs.mindrot.org:/cvs checkout openssh".
> >
> > I managed to generate a configure script via "autoreconf",
> > and the configure script appeared to work.
>
> That's expected, and covered in the INSTALL file

OK. I misread your message, which I had thought said to check out from
CVS HEAD, but I now see that that part of the instructions was for the
OpenBSD version of openssh, not for the portable version of openssh.

> > Surely the tests should use "-F /dev/null", or "-F
> > ${special_configuration_file}"?
>
> For the most part, it does use its own config files which it creates in
> a working directory during the test and removes afterward (see, eg,
> regress/connect.sh).
>
> It appears that just the multiplex tests in particular don't, but that's
> easily fixable, although that won't be until after the release.

OK.

> > This time, "make tests" succeeded. However, it created an empty
> > $HOME/.ssh directory. I think it's rude for a test suite to create
> > any non-temporary files or directories.
>
> That's a reasonable point, however offhand I can't think of a way to
> stop it.

Perhaps HOME=${path_to_temporary_directory} ?

--apb (Alan Barrett)
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@mindrot.org
https://lists.mindrot.org/mailman/li...enssh-unix-dev