Hi All.
OpenSSH 4.1 will be released in the next couple of weeks and we invite
interested parties to test a snapshot.
The changes since 4.0 are mostly bugfixes, for a detailed list see
http://bugzilla.mindrot.org/show_bug.cgi?id=994
Running the regression tests supplied with Portable does not require
installation and is a simply:
$ ./configure && make tests
Testing on suitable non-production systems is also appreciated. Please
send reports of success or failure to openssh-unix-dev at mindrot.org.
I believe that the issues reported during the 4.0 testing have been
resolved, however if there are issues that remain then please report them
again.
Snapshots are available at
ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/snapshot/
or one of its mirrors listed at http://www.openssh.com/portable.html#ftp
Thanks.
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
Hi Darren, On Apr 3 10:45, Darren Tucker wrote:> Hi All. > > OpenSSH 4.1 will be released in the next couple of weeks and we invite > interested parties to test a snapshot. > > The changes since 4.0 are mostly bugfixes, for a detailed list see > http://bugzilla.mindrot.org/show_bug.cgi?id=994 > > Running the regression tests supplied with Portable does not require > installation and is a simply: > > $ ./configure && make testsBuild and regression tests are running well on Cygwin. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat, Inc.
Hi, All the test cases passed on HP-UX 11.11 platform. Thanks -logu> Hi All. > > OpenSSH 4.1 will be released in the next couple of weeks and we invite > interested parties to test a snapshot. > > The changes since 4.0 are mostly bugfixes, for a detailed list see > http://bugzilla.mindrot.org/show_bug.cgi?id=994 > > Running the regression tests supplied with Portable does not require > installation and is a simply: > > $ ./configure && make tests > > Testing on suitable non-production systems is also appreciated. Please > send reports of success or failure to openssh-unix-dev at mindrot.org. > > I believe that the issues reported during the 4.0 testing have been > resolved, however if there are issues that remain then please report them > again. > > Snapshots are available at > ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/snapshot/ > or one of its mirrors listed at http://www.openssh.com/portable.html#ftp > > Thanks. > > -- > Darren Tucker (dtucker at zip.com.au) > GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 > Good judgement comes with experience. Unfortunately, the experience > usually comes from bad judgement. > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > http://www.mindrot.org/mailman/listinfo/openssh-unix-dev > >
On 2005-04-03 10:45:27 +1000, Darren Tucker wrote:> send reports of success or failure to openssh-unix-dev at mindrot.org.Everythings fine on SuSE 9.2 AMD64. Best regards Martin -- http://www.tm.oneiros.de
All tests pass for Solaris/Sparc 2.6, 7, 8, 9 On 2005-04-03 10:45:27 +1000, Darren Tucker wrote:> send reports of success or failure to openssh-unix-dev at mindrot.org._______________________________________________ openssh-unix-dev mailing list openssh-unix-dev at mindrot.org http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
Hi, On Sun, Apr 03, 2005 at 10:45:27AM +1000, Darren Tucker wrote:> The changes since 4.0 are mostly bugfixes, for a detailed list see > http://bugzilla.mindrot.org/show_bug.cgi?id=994 > > Running the regression tests supplied with Portable does not require > installation and is a simply: > > $ ./configure && make testsTesting vs. CVS as of today. SCO 3.2v4.2: configure: error: "This Platform is no longer supported." (well, that was just for completeness anyway) NetBSD 2.0.2 on Sparc64 (should find all endianness and word-size issues): - configure: WARNING: the operating system that you are using does not appear to support either the getpeereid() API nor the SO_PEERCRED getsockopt() option. These facilities are used to enforce security checks to prevent unauthorised connections to ssh-agent. Their absence increases the risk that a malicious user can connect to your agent. out of curiousity: who *does* support this, if not the BSDs? Or is it just NetBSD that can't do it yet? - make: all fine - make tests: ... reexec tests: proto 2 ok reexec tests run test brokenkeys.sh ... ok broken keys --> all fine good work! gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de
Once upon a time, Darren Tucker <dtucker at zip.com.au> said:> OpenSSH 4.1 will be released in the next couple of weeks and we invite > interested parties to test a snapshot.I tested openssh-SNAP-20050404.tar.gz on Tru64, and I needed this patch: ************************************************************************ diff -urN openssh-SNAP-20050404/auth-sia.c openssh/auth-sia.c --- openssh-SNAP-20050404/auth-sia.c Thu Mar 4 05:59:37 2004 +++ openssh/auth-sia.c Mon Apr 4 11:05:29 2005 @@ -47,7 +47,7 @@ extern char **saved_argv; int -sys_auth_passwd(Authctxt *authctxt, char *pass) +sys_auth_passwd(Authctxt *authctxt, const char *pass) { int ret; SIAENTITY *ent = NULL; diff -urN openssh-SNAP-20050404/auth-sia.h openssh/auth-sia.h --- openssh-SNAP-20050404/auth-sia.h Thu Mar 4 05:59:37 2004 +++ openssh/auth-sia.h Mon Apr 4 11:05:33 2005 @@ -26,7 +26,7 @@ #ifdef HAVE_OSF_SIA -int sys_auth_passwd(Authctxt *, char *); +int sys_auth_passwd(Authctxt *, const char *); void session_setup_sia(struct passwd *, char *); #endif /* HAVE_OSF_SIA */ ************************************************************************ I left the sys_auth_passwd() declaration in auth-sia.h, but should it be removed (and also removed from the top of auth-passwd.c)? Both also include auth.h which now declares sys_auth_passwd() as well. Aside from that, all tests pass. -- Chris Adams <cmadams at hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
Solaris 5.10
Config works fine.
Make works fine.
Make tests - fails.
Master running (pid=21217)
Exit request sent.
failed connection multiplexing
*** Error code 1
The following command caused the error:
if [ "xconnect.sh proxy-connect.sh connect-privsep.sh proto-version.sh
proto-
mismatch.sh exit-status.sh envpass.sh transfer.sh banner.sh rekey.sh stderr-
data.sh stderr-after-eof.sh broken-pipe.sh try-ciphers.sh yes-head.sh login-
timeout.sh agent.sh agent-getpeereid.sh agent-timeout.sh agent-ptrace.sh
keyscan.sh keygen-change.sh scp.sh sftp.sh sftp-cmds.sh sftp-badcmds.sh sftp-
batch.sh sftp-glob.sh reconfigure.sh dynamic-forward.sh forwarding.sh
multiplex.sh reexec.sh brokenkeys.sh" = "x" ]; then exit 0; fi; \
for TEST in ""connect.sh proxy-connect.sh connect-privsep.sh
proto-version.sh
proto-mismatch.sh exit-status.sh envpass.sh transfer.sh banner.sh rekey.sh
stderr-data.sh stderr-after-eof.sh broken-pipe.sh try-ciphers.sh yes-head.sh
login-timeout.sh agent.sh agent-getpeereid.sh agent-timeout.sh agent-ptrace.sh
keyscan.sh keygen-change.sh scp.sh sftp.sh sftp-cmds.sh sftp-badcmds.sh sftp-
batch.sh sftp-glob.sh reconfigure.sh dynamic-forward.sh forwarding.sh
multiplex.sh reexec.sh brokenkeys.sh; do \
echo "run test ${TEST}" ... 1>&2; \
(env SUDO= sh /tech_svc/SSH/openssh-SNAP-20050404/regress/test-
exec.sh /tech_svc/SSH/openssh-SNAP-20050404/regress /tech_svc/SSH/openssh-SNAP-
20050404/regress/${TEST}) || exit $?; \
done
make: Fatal error: Command failed for target `t-exec'
Current working directory /tech_svc/SSH/openssh-SNAP-20050404/regress
*** Error code 1
make: Fatal error: Command failed for target `tests'
----
Also, still showing loads of the following message in syslog output
Apr 4 15:52:12 srvname sshd[14794]: [ID 800047 auth.error] error: setsockopt
SO_KEEPALIVE: Socket operation on non-socket
Apr 4 15:52:13 srvname sshd[14796]: [ID 800047 auth.error] error: setsockopt
SO_KEEPALIVE: Socket operation on non-socket
On Solaris10/Sparc: My first make tests failed as below. Running again, all tests pass. I then started again with a clean directory and did configure && make tests without errors. Pehaps this is just wierdness on my system but perhaps someone else will see something obvious. run test agent.sh ... Error reading response length from authentication socket. Permission denied. agent fwd proto 1 failed (exit code 0) failed simple agent test gmake[1]: *** [t-exec] Error 1 gmake[1]: Leaving directory `/usr/local/src/openssh-SNAP-20050404/regress' gmake: *** [tests] Error 2 -----Original Message----- From: openssh-unix-dev-bounces+bob.edgar=commerzbankib.com at mindrot.org [mailto:openssh-unix-dev-bounces+bob.edgar=commerzbankib.com at mindrot.org ]On Behalf Of Edgar, Bob Sent: Montag, 4. April 2005 15:51 To: 'openssh-unix-dev at mindrot.org' Subject: RE: OpenSSH 4.1: call for testing. All tests pass for Solaris/Sparc 2.6, 7, 8, 9 On 2005-04-03 10:45:27 +1000, Darren Tucker wrote:> send reports of success or failure to openssh-unix-dev at mindrot.org._______________________________________________ openssh-unix-dev mailing list openssh-unix-dev at mindrot.org http://www.mindrot.org/mailman/listinfo/openssh-unix-dev _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev at mindrot.org http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
Chris Adams wrote:> I tested openssh-SNAP-20050404.tar.gz on Tru64, and I needed this patch:Applied, thanks.> I left the sys_auth_passwd() declaration in auth-sia.h, but should it be > removed (and also removed from the top of auth-passwd.c)?Agreed, also done.> Aside from that, all tests pass.Thanks! -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
No, I'm using 0.9.7d compiled on Sol9 (this is a bootstrap operation to build a new set of tools for Sol10). I didn't do anything between the first test and the second except to add a -k switch to gmake to have it run the rest of the tests. The second run didn't fail (as I indicated) so I made a new empty directory followed by a configure/make and it too didn't fail. I then untarred a new copy of everything and repeated and that too didn't fail. As I said, this may just be something bogus on my system. I only posted so that if someone else saw something similar they'd see it had been seen before and I hoped that it might go click with one of the developers. -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Dienstag, 5. April 2005 12:31 To: Edgar, Bob Cc: 'openssh-unix-dev at mindrot.org' Subject: Re: OpenSSH 4.1: call for testing. Edgar, Bob wrote:> On Solaris10/Sparc: > > My first make tests failed as below. Running again, all tests pass. > I then started again with a clean directory and did configure && maketests> without errors. Pehaps this is just wierdness on my system but perhaps > someone else will see something obvious.No, nothing obvious. One possibility: if you're using OpenSSL <= 0.9.7e compiled on Solaris 10, it won't use the /dev/*random devices. This means that the ssh-rand-helper needs to exist in its final location (/usr/local/libexec by default) in order for the tests to run (so if it started working after a "make install" then that's probably the reason). -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On our Solaris 10/Sparc platform, I have loaded vanilla OpenSSL 0.9.7f, and have added the --with-ssl-dir=/usr/local/ssl to the config. did gmake distclean to clear things up. re-ran config re-ran gmake re-ran gmake tests Failed on multiplexing (probably due to the SO_KEEPALIVE: Socket Operation on non-socket) issue. re-re-ran gmake tests with -k param same error.
> This is due to a bug in OpenSSL; they use the option O_NOFOLLOW on > opening the /dev/random devices -- and, on Solaris, this is a no-no, as > /dev/random is a symlink to /devices/pseudo/[blah blah].Which is why I went with OpenSSL 0.9.7f - as that problem has been fixed in this release.
It appears to be the ls.copy file creation that's failing...
gmake tests LTESTS=multiplex
(cd openbsd-compat && gmake)
gmake[1]: Entering directory `/tech_svc/SSH/openssh-4.0p1/openbsd-compat'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/tech_svc/SSH/openssh-4.0p1/openbsd-compat'
BUILDDIR=`pwd`; \
[ -d `pwd`/regress ] || mkdir -p `pwd`/regress; \
[ -f `pwd`/regress/Makefile ] || \
ln -s `cd . && pwd`/regress/Makefile `pwd`/regress/Makefile ; \
TEST_SHELL="sh"; \
TEST_SSH_SSH="${BUILDDIR}/ssh"; \
TEST_SSH_SSHD="${BUILDDIR}/sshd"; \
TEST_SSH_SSHAGENT="${BUILDDIR}/ssh-agent"; \
TEST_SSH_SSHADD="${BUILDDIR}/ssh-add"; \
TEST_SSH_SSHKEYGEN="${BUILDDIR}/ssh-keygen"; \
TEST_SSH_SSHKEYSCAN="${BUILDDIR}/ssh-keyscan"; \
TEST_SSH_SFTP="${BUILDDIR}/sftp"; \
TEST_SSH_SFTPSERVER="${BUILDDIR}/sftp-server"; \
cd ./regress || exit $?; \
gmake \
.OBJDIR="${BUILDDIR}/regress" \
.CURDIR="`pwd`" \
BUILDDIR="${BUILDDIR}" \
OBJ="${BUILDDIR}/regress/" \
PATH="${BUILDDIR}:${PATH}" \
TEST_SHELL="${TEST_SHELL}" \
TEST_SSH_SSH="${TEST_SSH_SSH}" \
TEST_SSH_SSHD="${TEST_SSH_SSHD}" \
TEST_SSH_SSHAGENT="${TEST_SSH_SSHAGENT}" \
TEST_SSH_SSHADD="${TEST_SSH_SSHADD}" \
TEST_SSH_SSHKEYGEN="${TEST_SSH_SSHKEYGEN}" \
TEST_SSH_SSHKEYSCAN="${TEST_SSH_SSHKEYSCAN}" \
TEST_SSH_SFTP="${TEST_SSH_SFTP}" \
TEST_SSH_SFTPSERVER="${TEST_SSH_SFTPSERVER}" \
EXEEXT="" \
tests
gmake[1]: Entering directory `/tech_svc/SSH/openssh-4.0p1/regress'
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/rsa_ssh2.prv | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.prv
cat /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.prv >
/tech_svc/SSH/openssh-4.0p1/regress//t2.out
chmod 600 /tech_svc/SSH/openssh-4.0p1/regress//t2.out
ssh-keygen -yf /tech_svc/SSH/openssh-4.0p1/regress//t2.out | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub
ssh-keygen -ef
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub>/tech_svc/SSH/openssh-4.0p1/regress//rsa_secsh.pub
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress//rsa_secsh.pub | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub
rm -f /tech_svc/SSH/openssh-4.0p1/regress/rsa_secsh.pub
ssh-keygen -lf /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub |\
awk '{print $2}' | diff -
/tech_svc/SSH/openssh-4.0p1/regress/t4.ok
ssh-keygen -Bf /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub |\
awk '{print $2}' | diff -
/tech_svc/SSH/openssh-4.0p1/regress/t5.ok
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/dsa_ssh2.prv >
/tech_svc/SSH/openssh-4.0p1/regress//t6.out1
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/dsa_ssh2.pub >
/tech_svc/SSH/openssh-4.0p1/regress//t6.out2
chmod 600 /tech_svc/SSH/openssh-4.0p1/regress//t6.out1
ssh-keygen -yf /tech_svc/SSH/openssh-4.0p1/regress//t6.out1 | diff -
/tech_svc/SSH/openssh-4.0p1/regress//t6.out2
ssh-keygen -lf /tech_svc/SSH/openssh-4.0p1/regress//t7.out > /dev/null
ssh-keygen -Bf /tech_svc/SSH/openssh-4.0p1/regress//t7.out > /dev/null
run test multiplex.sh ...
test connection multiplexing: envpass
test connection multiplexing: transfer
scp: failed copy /bin/ls
cmp: cannot open /tech_svc/SSH/openssh-4.0p1/regress/ls.copy
scp: corrupted copy of /bin/ls
test connection multiplexing: status 0
test connection multiplexing: status 1
test connection multiplexing: status 4
test connection multiplexing: status 5
test connection multiplexing: status 44
Master running (pid=23831)
Exit request sent.
failed connection multiplexing
gmake[1]: *** [t-exec] Error 1
gmake[1]: Leaving directory `/tech_svc/SSH/openssh-4.0p1/regress'
gmake: *** [tests] Error 2
> Thanks for testing.
>
> guyverdh at mchsi.com wrote:
> > Solaris 5.10
> >
> > Config works fine.
> >
> > Make works fine.
> >
> > Make tests - fails.
> >
> > Master running (pid=21217)
> > Exit request sent.
> > failed connection multiplexing
>
> So far I've not been able to reproduce this (Sol10/x86).
>
> Is there any output from before this line? Could you run the multiplex
> test on its own and send the output? ie
>
> $ make tests LTESTS=multiplex
>
> [...]
> > Also, still showing loads of the following message in syslog output
> >
> > Apr 4 15:52:12 srvname sshd[14794]: [ID 800047 auth.error] error:
setsockopt
> > SO_KEEPALIVE: Socket operation on non-socket
> > Apr 4 15:52:13 srvname sshd[14796]: [ID 800047 auth.error] error:
setsockopt
> > SO_KEEPALIVE: Socket operation on non-socket
>
> While annoying, this is harmless. It will be fixed after 4.1.
>
> --
> Darren Tucker (dtucker at zip.com.au)
> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
> Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.
I had already removed the "SunSSH" packages.
I have yet to "make install" the new code yet, so the PATH'ing
shouldn't have
been an issue.
I did, however, add /tech_svc/SSH/opessn-4.0p1 to the PATH env-var, and re-ran
the gmake tests LTESTS=multiplex
with no changes apparent
I then modified my PATH to include ./ as the last element, with no differences.
Then I changed the entry /bin/ls to /usr/bin/ls since /bin is a sym-link to
/usr/bin, with no change in output.
I finally ran gmake install, then re-ran the tests, and the tests succeeded.
ie - apparently, it's trying to run SCP from the installed directory,
instead of
the directory where it had been compiled.
Wouldn't we want tests to succeed, before running the install?
gmake tests LTESTS=multiplex
(cd openbsd-compat && gmake)
gmake[1]: Entering directory `/tech_svc/SSH/openssh-4.0p1/openbsd-compat'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/tech_svc/SSH/openssh-4.0p1/openbsd-compat'
BUILDDIR=`pwd`; \
[ -d `pwd`/regress ] || mkdir -p `pwd`/regress; \
[ -f `pwd`/regress/Makefile ] || \
ln -s `cd . && pwd`/regress/Makefile `pwd`/regress/Makefile ; \
TEST_SHELL="sh"; \
TEST_SSH_SSH="${BUILDDIR}/ssh"; \
TEST_SSH_SSHD="${BUILDDIR}/sshd"; \
TEST_SSH_SSHAGENT="${BUILDDIR}/ssh-agent"; \
TEST_SSH_SSHADD="${BUILDDIR}/ssh-add"; \
TEST_SSH_SSHKEYGEN="${BUILDDIR}/ssh-keygen"; \
TEST_SSH_SSHKEYSCAN="${BUILDDIR}/ssh-keyscan"; \
TEST_SSH_SFTP="${BUILDDIR}/sftp"; \
TEST_SSH_SFTPSERVER="${BUILDDIR}/sftp-server"; \
cd ./regress || exit $?; \
gmake \
.OBJDIR="${BUILDDIR}/regress" \
.CURDIR="`pwd`" \
BUILDDIR="${BUILDDIR}" \
OBJ="${BUILDDIR}/regress/" \
PATH="${BUILDDIR}:${PATH}" \
TEST_SHELL="${TEST_SHELL}" \
TEST_SSH_SSH="${TEST_SSH_SSH}" \
TEST_SSH_SSHD="${TEST_SSH_SSHD}" \
TEST_SSH_SSHAGENT="${TEST_SSH_SSHAGENT}" \
TEST_SSH_SSHADD="${TEST_SSH_SSHADD}" \
TEST_SSH_SSHKEYGEN="${TEST_SSH_SSHKEYGEN}" \
TEST_SSH_SSHKEYSCAN="${TEST_SSH_SSHKEYSCAN}" \
TEST_SSH_SFTP="${TEST_SSH_SFTP}" \
TEST_SSH_SFTPSERVER="${TEST_SSH_SFTPSERVER}" \
EXEEXT="" \
tests
gmake[1]: Entering directory `/tech_svc/SSH/openssh-4.0p1/regress'
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/rsa_ssh2.prv | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.prv
cat /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.prv >
/tech_svc/SSH/openssh-4.0p1/regress//t2.out
chmod 600 /tech_svc/SSH/openssh-4.0p1/regress//t2.out
ssh-keygen -yf /tech_svc/SSH/openssh-4.0p1/regress//t2.out | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub
ssh-keygen -ef
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub>/tech_svc/SSH/openssh-4.0p1/regress//rsa_secsh.pub
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress//rsa_secsh.pub | diff -
/tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub
rm -f /tech_svc/SSH/openssh-4.0p1/regress/rsa_secsh.pub
ssh-keygen -lf /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub |\
awk '{print $2}' | diff -
/tech_svc/SSH/openssh-4.0p1/regress/t4.ok
ssh-keygen -Bf /tech_svc/SSH/openssh-4.0p1/regress/rsa_openssh.pub |\
awk '{print $2}' | diff -
/tech_svc/SSH/openssh-4.0p1/regress/t5.ok
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/dsa_ssh2.prv >
/tech_svc/SSH/openssh-4.0p1/regress//t6.out1
ssh-keygen -if /tech_svc/SSH/openssh-4.0p1/regress/dsa_ssh2.pub >
/tech_svc/SSH/openssh-4.0p1/regress//t6.out2
chmod 600 /tech_svc/SSH/openssh-4.0p1/regress//t6.out1
ssh-keygen -yf /tech_svc/SSH/openssh-4.0p1/regress//t6.out1 | diff -
/tech_svc/SSH/openssh-4.0p1/regress//t6.out2
ssh-keygen -lf /tech_svc/SSH/openssh-4.0p1/regress//t7.out > /dev/null
ssh-keygen -Bf /tech_svc/SSH/openssh-4.0p1/regress//t7.out > /dev/null
run test multiplex.sh ...
test connection multiplexing: envpass
test connection multiplexing: transfer
test connection multiplexing: status 0
test connection multiplexing: status 1
test connection multiplexing: status 4
test connection multiplexing: status 5
test connection multiplexing: status 44
Master running (pid=24948)
Exit request sent.
ok connection multiplexing
gmake[1]: Leaving directory `/tech_svc/SSH/openssh-4.0p1/regress'
> guyverdh at mchsi.com wrote:
> > It appears to be the ls.copy file creation that's failing...
> [...]
> > scp: failed copy /bin/ls
> > cmp: cannot open /tech_svc/SSH/openssh-4.0p1/regress/ls.copy
> > scp: corrupted copy of /bin/ls
>
> Ah, I'll bet that either scp is not in the server's $PATH, or that
the
> first one in the path is the SunSSH one.
>
> --
> Darren Tucker (dtucker at zip.com.au)
> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
> Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.
openssh-SNAP-20050408 running Solaris 8, Sun Forte C
compiler, 64-bit.
Output of configure:
OpenSSH has been configured with the following
options:
User binaries: /opt/local/bin
System binaries: /opt/local/sbin
Configuration files: /etc
Askpass program:
/opt/local/libexec/ssh-askpass
Manual pages:
/opt/local/man/manX
PID file: /var/run
Privilege separation chroot path: /var/empty
sshd default user PATH:
/usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin
(If PATH is set in /etc/default/login it will be
used instead. If
used, ensure the path to scp is present, otherwise
scp will not work.)
Manpage format: man
PAM support: yes
KerberosV support: no
Smartcard support: no
S/KEY support: no
TCP Wrappers support: no
MD5 password support: no
libedit support: no
IP address in $DISPLAY hack: no
Translate v4 in v6 hack: no
BSD Auth support: no
Random number source: OpenSSL internal
ONLY
Host: sparc-sun-solaris2.8
Compiler: cc
Compiler flags: -xtarget=ultra -xarch=v9 -mt
Preprocessor flags: -I/opt/local/ssl/include
-D_XOPEN_SOURCE=500 -D__EXTENSIONS__
Linker flags: -L/opt/local/ssl/lib/64
-R/opt/local/ssl/lib/64 -xtarget=ultra -xarch=v9
Libraries: -lpam -ldl -lresolv -lcrypto -lrt
-lz -lsocket -lnsl
make tests ran with no errors reported.
Cheers,
-Thomas
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com