#3114 closed task (fixed)
OpenSSH 5.6p1
Reported by: | Ivan Wagner | Owned by: | Randy McMurchy |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
Just compiled OpenSSH 5.5p1 against OpenSSL 1.0.0 and Linux-PAM 1.1.1 and have a few notes about the test suite.
after make, test suite is failing during the test of multiple.sh with the following error:
"test connection multiplexing: transfer
scp: failed copy /bin/ls
cmp: /sources/openssh-5.5p1/regress/ls.copy: No such file or directory
scp: corrupted copy of /bin/ls
failed connection multiplexing
make[1]: * [t-exec] Error 1
make[1]: Leaving directory `/sources/openssh-5.5p1/regress'
make: * [tests] Error 2"
Found a workaround in the BLFS mail archives (see http://linuxfromscratch.org/pipermail/blfs-dev/2008-February/018019.html), which suggested installing openssh and re-running test suite. Test suite passed once openssh was installed.
One of the test is being skipped for some reason and can be enabled by doing "export SUDO=<path to sudo>":
"run test agent-getpeereid.sh ...
skipped: need SUDO to switch to uid nobody"
This test passed for me only when openssh was installed.
Change History (6)
comment:1 by , 13 years ago
Summary: | OpenSSH 5.5p1 test suite workarounds → OpenSSH 5.6p1 |
---|
comment:2 by , 13 years ago
The testsuite in 5.6p1 does fail very quickly if the priv-separation directory /var/lib/sshd does not exist.
comment:4 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
My latest observation (with SUDO installed and the /var/lib/sshd directory created), the test suite finishes with all tests passing. Note that I am mentioning the /var/lib/sshd directory because if you do DESTDIR installs, the testsuite will bomb because the directory does not exist.
Updated BLFS to OpenSSH-5.6p1
Version increment to 5.6p1
http://openssh.org/
Note that this ticket was initially opened for the test suite workaround. I'm not sure there is anything we need to do for this "workaround". The book already says to copy sftp to the system before running the test, and we can't do anything about sudo. It may or may not be installed.
A note about sudo in the test suite instructions should be enough (after it is confirmed that it works)