Chahine, Nagib N
2003-Nov-20 16:59 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
Hi, Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I located the error message and turned debugging on in packet.c which dumps the content of the packet. What I see is a packet with length 5 bytes which confuses the client's side. I tried running the sshd version 3.7.1p2 to match the client I keep getting the same error. RUNNING WITH -1 OPTION: ----------------------- sh-2.05# ssh 192.168.1.1 -1 -l root incoming packet length= 267 read_poll plain: 0000 0000 0002 41f2 5ed2 a112 7e29 0000 0300 0006 2303 00d8 bf4a 5f8f 0f80 8fb9 6311 30d2 66cb e6e0 10c5 7cfe b7c2 60b4 ee32 97fe ed99 9606 8357 affb 10f7 578a 63ee 592c 9730 92b6 f3d2 8274 62cc 250d af16 5685 e40d d5eb b9d9 bbd8 4404 3bda 473e ccd4 6852 947d 90f9 5963 55cd 63f0 0c9b f564 e041 8100 0004 0000 0623 0400 a7f8 81dc 5627 07bc 7ab9 af88 daf8 ad7a ae43 6fbc bc8a 8f69 26e6 9481 f998 54f3 f5d5 d66d db13 366c ae9c fe6d 08c7 df7f 924c bce4 6ce9 0635 2200 b373 2b74 6d6f 96a6 4e65 3c21 a735 3e6a 6ab3 63c7 eeb4 4d1d 41c0 0c86 9818 bb0f 10df 9f8f a8dd bcc3 d3dc 807e f5dc 6080 7205 cf88 eb5d bef3 a4ce a17c 7853 70c9 ebab 7f7a 8601 0000 0002 0000 0048 0000 002c 3efb f1c5 stored_cheksum = 3efbf1c5 calculated_cheksum = 3efbf1c5 packet_send plain: 0000 0000 0303 41f2 5ed2 a112 7e29 03ff 7095 fd74 29ac 0a29 3201 8556 64bc 4b27 dc4d c8b2 e789 f1b0 7be5 899c b5a4 494e e114 7453 29f3 846e f923 5eea 35d4 07c7 c2d8 28f2 167f a5ba 01ad 6274 cfc1 c64c 9f24 da82 fbcd 6d81 1c66 4ff8 0484 1b62 12b8 d83e 37a2 00b3 abde 85f1 ca1b bf80 1864 8b6c d5c4 1ad8 819e 59b5 6331 ee5f 4814 cfb6 c439 dd42 edc0 a9f8 99fd 1969 0000 0003 705b 27e1 encrypted: 0000 0094 0000 0000 0303 41f2 5ed2 a112 7e29 03ff 7095 fd74 29ac 0a29 3201 8556 64bc 4b27 dc4d c8b2 e789 f1b0 7be5 899c b5a4 494e e114 7453 29f3 846e f923 5eea 35d4 07c7 c2d8 28f2 167f a5ba 01ad 6274 cfc1 c64c 9f24 da82 fbcd 6d81 1c66 4ff8 0484 1b62 12b8 d83e 37a2 00b3 abde 85f1 ca1b bf80 1864 8b6c d5c4 1ad8 819e 59b5 6331 ee5f 4814 cfb6 c439 dd42 edc0 a9f8 99fd 1969 0000 0003 705b 27e1 incoming packet length= 5 read_poll plain: a425 9ac0 a3f9 8a22 stored_cheksum = a3f98a22 calculated_cheksum = ec45aa79 Disconnecting: Corrupted check bytes on input. packet_send plain: 1a03 bc22 1896 9f52 0100 0000 1f43 6f72 7275 7074 6564 2063 6865 636b 2062 7974 6573 206f 6e20 696e 7075 742e 1f61 9863 encrypted: 0000 0028 f66c 265c b9d8 734d a622 507a 0ca2 1c47 37d5 6b23 d1e0 1bdd ed09 6461 3b87 df96 14a9 3698 d5e6 ee48 b758 8461 a2aa 0fc7 sh-2.05# RUNNING WITH -2 OPTION (partial dump) ------------------------------------- plain: 0000 0000 0015 encrypted: 0000 000c 0a15 0000 0000 0000 0000 0000 read_poll enc/full: 0000 0000 0000 0000 read/plain[21]: plain: 0000 0000 0005 0000 000c 7373 682d 7573 6572 6175 7468 encrypted: 442e 1233 1453 2f88 002f 2b0b e2bf d26f 38b7 eb9b dfb5 5003 6fda e4d4 ff8b 3bc0 2757 4ec5 884f e0db 94b5 e41e 5f2c 1c1d read_poll enc/full: 966f 20eb 8eb6 7ff2 5661 c8f0 7738 3de5 5e10 81e2 05ba e0af 9a0f 1cbc bc24 8687 b1bc 3e3e 13ec d372 13f8 91ae 5d18 f95e Disconnecting: Corrupted MAC on input. plain: 0000 0000 0001 0000 0002 0000 0017 436f 7272 7570 7465 6420 4d41 4320 6f6e 2069 6e70 7574 2e00 0000 00 encrypted: 9ba6 8f38 fb65 d36d 02a0 413a 2c02 debd 1a91 9f8b 305e 7614 88df 2ba1 72f7 f58e 4ecc 0398 220c 59b3 2c1d 197e 4ac4 9f30 f313 f2d4 1850 10c8 205e 3f83 45f5 b1f9 I would appreciate any hints from anyone who can give me some hints. Thanks Nagib Chahine
Chahine, Nagib N
2003-Nov-24 16:19 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
Hi, Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I located the error message and turned debugging on in packet.c which dumps the content of the packet. What I see is a packet with length 5 bytes which confuses the client's side. I tried running the sshd version 3.7.1p2 to match the client I keep getting the same error. RUNNING WITH -1 OPTION: ----------------------- sh-2.05# ssh 192.168.1.1 -1 -l root incoming packet length= 267 read_poll plain: 0000 0000 0002 41f2 5ed2 a112 7e29 0000 0300 0006 2303 00d8 bf4a 5f8f 0f80 8fb9 6311 30d2 66cb e6e0 10c5 7cfe b7c2 60b4 ee32 97fe ed99 9606 8357 affb 10f7 578a 63ee 592c 9730 92b6 f3d2 8274 62cc 250d af16 5685 e40d d5eb b9d9 bbd8 4404 3bda 473e ccd4 6852 947d 90f9 5963 55cd 63f0 0c9b f564 e041 8100 0004 0000 0623 0400 a7f8 81dc 5627 07bc 7ab9 af88 daf8 ad7a ae43 6fbc bc8a 8f69 26e6 9481 f998 54f3 f5d5 d66d db13 366c ae9c fe6d 08c7 df7f 924c bce4 6ce9 0635 2200 b373 2b74 6d6f 96a6 4e65 3c21 a735 3e6a 6ab3 63c7 eeb4 4d1d 41c0 0c86 9818 bb0f 10df 9f8f a8dd bcc3 d3dc 807e f5dc 6080 7205 cf88 eb5d bef3 a4ce a17c 7853 70c9 ebab 7f7a 8601 0000 0002 0000 0048 0000 002c 3efb f1c5 stored_cheksum = 3efbf1c5 calculated_cheksum = 3efbf1c5 packet_send plain: 0000 0000 0303 41f2 5ed2 a112 7e29 03ff 7095 fd74 29ac 0a29 3201 8556 64bc 4b27 dc4d c8b2 e789 f1b0 7be5 899c b5a4 494e e114 7453 29f3 846e f923 5eea 35d4 07c7 c2d8 28f2 167f a5ba 01ad 6274 cfc1 c64c 9f24 da82 fbcd 6d81 1c66 4ff8 0484 1b62 12b8 d83e 37a2 00b3 abde 85f1 ca1b bf80 1864 8b6c d5c4 1ad8 819e 59b5 6331 ee5f 4814 cfb6 c439 dd42 edc0 a9f8 99fd 1969 0000 0003 705b 27e1 encrypted: 0000 0094 0000 0000 0303 41f2 5ed2 a112 7e29 03ff 7095 fd74 29ac 0a29 3201 8556 64bc 4b27 dc4d c8b2 e789 f1b0 7be5 899c b5a4 494e e114 7453 29f3 846e f923 5eea 35d4 07c7 c2d8 28f2 167f a5ba 01ad 6274 cfc1 c64c 9f24 da82 fbcd 6d81 1c66 4ff8 0484 1b62 12b8 d83e 37a2 00b3 abde 85f1 ca1b bf80 1864 8b6c d5c4 1ad8 819e 59b5 6331 ee5f 4814 cfb6 c439 dd42 edc0 a9f8 99fd 1969 0000 0003 705b 27e1 incoming packet length= 5 read_poll plain: a425 9ac0 a3f9 8a22 stored_cheksum = a3f98a22 calculated_cheksum = ec45aa79 Disconnecting: Corrupted check bytes on input. packet_send plain: 1a03 bc22 1896 9f52 0100 0000 1f43 6f72 7275 7074 6564 2063 6865 636b 2062 7974 6573 206f 6e20 696e 7075 742e 1f61 9863 encrypted: 0000 0028 f66c 265c b9d8 734d a622 507a 0ca2 1c47 37d5 6b23 d1e0 1bdd ed09 6461 3b87 df96 14a9 3698 d5e6 ee48 b758 8461 a2aa 0fc7 sh-2.05# RUNNING WITH -2 OPTION (partial dump) ------------------------------------- plain: 0000 0000 0015 encrypted: 0000 000c 0a15 0000 0000 0000 0000 0000 read_poll enc/full: 0000 0000 0000 0000 read/plain[21]: plain: 0000 0000 0005 0000 000c 7373 682d 7573 6572 6175 7468 encrypted: 442e 1233 1453 2f88 002f 2b0b e2bf d26f 38b7 eb9b dfb5 5003 6fda e4d4 ff8b 3bc0 2757 4ec5 884f e0db 94b5 e41e 5f2c 1c1d read_poll enc/full: 966f 20eb 8eb6 7ff2 5661 c8f0 7738 3de5 5e10 81e2 05ba e0af 9a0f 1cbc bc24 8687 b1bc 3e3e 13ec d372 13f8 91ae 5d18 f95e Disconnecting: Corrupted MAC on input. plain: 0000 0000 0001 0000 0002 0000 0017 436f 7272 7570 7465 6420 4d41 4320 6f6e 2069 6e70 7574 2e00 0000 00 encrypted: 9ba6 8f38 fb65 d36d 02a0 413a 2c02 debd 1a91 9f8b 305e 7614 88df 2ba1 72f7 f58e 4ecc 0398 220c 59b3 2c1d 197e 4ac4 9f30 f313 f2d4 1850 10c8 205e 3f83 45f5 b1f9 I would appreciate any hints from anyone who can give me some hints. Thanks Nagib Chahine
Markus Friedl
2003-Nov-24 17:44 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
so is the packet decrypted correctly? or are both the HMAC and the decrypted packet wrong? In-Reply-To: <4543EA9DB1099E4583484B56803D0BFA0117FD71 at xch-sw-02.sw.nos.boeing.com> On Mon, Nov 24, 2003 at 08:19:33AM -0800, Chahine, Nagib N wrote:> Hi, > > Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. > > I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I located the error message and turned debugging on in packet.c which dumps the content of the packet. What I see is a packet with length 5 bytes which confuses the client's side. I tried running the sshd version 3.7.1p2 to match the client I keep getting the same error.
Chahine, Nagib N
2003-Nov-24 20:50 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
I am not able to tell whether it is decripted correctly, however as you see from the messages, I know the connection is established correctly, one message is received and decoded correctly since the checksum matches, howver one message coming from the server with length 5 bytes gets handled incorrectly by the client which yields to a bad checksum. Any ideas?? Nagib -----Original Message----- From: Markus Friedl [mailto:markus at openbsd.org] Sent: Mon 11/24/2003 9:44 AM To: Chahine, Nagib N Cc: openssh-unix-dev at mindrot.org Subject: Re: Problem running SSH on IBM PPC440 processor, help appreciated so is the packet decrypted correctly? or are both the HMAC and the decrypted packet wrong? In-Reply-To: <4543EA9DB1099E4583484B56803D0BFA0117FD71 at xch-sw-02.sw.nos.boeing.com> On Mon, Nov 24, 2003 at 08:19:33AM -0800, Chahine, Nagib N wrote:> Hi, > > Sorry to bother you on this mailing list, however I tried everything else and I am desperate to get this running. Please send me any hints you can think of. > > I have installed openssh-3.7.1p2 on a ppc target and trying to connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting the error "Disconnecting: Corrupted check bytes on input" no matter what I tried. I located the error message and turned debugging on in packet.c which dumps the content of the packet. What I see is a packet with length 5 bytes which confuses the client's side. I tried running the sshd version 3.7.1p2 to match the client I keep getting the same error.
Darren Tucker
2003-Nov-25 10:07 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
On Mon, Nov 24, 2003 at 08:19:33AM -0800, Chahine, Nagib N wrote:> I have installed openssh-3.7.1p2 on a ppc target and trying to > connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting > the error "Disconnecting: Corrupted check bytes on input" no matter what I tried.When you built OpenSSL, did you run the "make test" target, and did all the tests pass? -- 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.
Markus Friedl
2003-Nov-25 10:36 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
On Mon, Nov 24, 2003 at 12:50:29PM -0800, Chahine, Nagib N wrote:> I am not able to tell whether it is decripted correctly, however as you see from the messages, I know the connection is established correctly, one message is received and decoded correctly since the checksum matches, howver one message coming from the server with length 5 bytes gets handled incorrectly by the client which yields to a bad checksum.if you want to figure out if encryption/decryption is broken you should enable this kind of debugging on both hosts and compare the plaintext/encrypted packets.
Chahine, Nagib N
2003-Nov-25 16:14 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
Hi Darren, Thanks for your response, however there is no test target in the Makefile. There is a logintest: target and when I make it I get the following error: (cd openbsd-compat && make) make[1]: Entering directory `/home/nchahine/openssh-3.7.1p2/openbsd-compat' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/nchahine/openssh-3.7.1p2/openbsd-compat' gcc -o logintest logintest.o -L. -Lopenbsd-compat/ loginrec.o -lopenbsd-compat -lssh -lutil -l ./libssh.a(log.o): In function `do_log': /home/nchahine/openssh-3.7.1p2/log.c:396: undefined reference to `strnvis' /home/nchahine/openssh-3.7.1p2/log.c:396: relocation truncated to fit: R_PPC_REL24 strnvis collect2: ld returned 1 exit status make: *** [logintest] Error 1 -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tue 11/25/2003 2:07 AM To: Chahine, Nagib N Cc: openssh-unix-dev at mindrot.org Subject: Re: Problem running SSH on IBM PPC440 processor, help appreciated On Mon, Nov 24, 2003 at 08:19:33AM -0800, Chahine, Nagib N wrote:> I have installed openssh-3.7.1p2 on a ppc target and trying to > connect to an sshd running on a redhat 9 with openssh-3.5p1. I keep getting > the error "Disconnecting: Corrupted check bytes on input" no matter what I tried.When you built OpenSSL, did you run the "make test" target, and did all the tests pass? -- 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.
Chahine, Nagib N
2003-Nov-25 17:38 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
Thanks Ben, I was looking for test: and missed it.
Ok when I make tests I get the following error:
sh-2.05# make tests
(cd openbsd-compat && make)
make[1]: Entering directory `/home/nchahine/openssh-3.7.1p2/openbsd-compat'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/nchahine/openssh-3.7.1p2/openbsd-compat'
/usr/bin/ar rv libssh.a authfd.o authfile.o bufaux.o buffer.o canohost.o
channels.o cipher.o cor - authfd.o
r - authfile.o
r - bufaux.o
r - buffer.o
r - canohost.o
r - channels.o
r - cipher.o
r - cipher-aes.o
r - cipher-bf1.o
r - cipher-ctr.o
r - cipher-3des1.o
r - compat.o
r - compress.o
r - crc32.o
r - deattack.o
r - fatal.o
r - hostfile.o
r - log.o
r - match.o
r - moduli.o
r - mpaux.o
r - nchan.o
r - packet.o
r - readpass.o
r - rsa.o
r - tildexpand.o
r - ttymodes.o
r - xmalloc.o
r - atomicio.o
r - key.o
r - dispatch.o
r - kex.o
r - mac.o
r - uuencode.o
r - misc.o
r - rijndael.o
r - ssh-dss.o
r - ssh-rsa.o
r - dh.o
r - kexdh.o
r - kexgex.o
r - kexdhc.o
r - kexgexc.o
r - scard.o
r - msg.o
r - progressmeter.o
r - dns.o
r - entropy.o
r - scard-opensc.o
r - gss-genr.o
ranlib libssh.a
BUILDDIR=`pwd`; \
[ -d `pwd`/regress ] || mkdir -p `pwd`/regress; \
[ -f `pwd`/regress/Makefile ] || \
ln -s ./regress/Makefile `pwd`/regress/Makefile ; \
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 $?; \
make \
.OBJDIR="${BUILDDIR}/regress" \
.CURDIR="`pwd`" \
BUILDDIR="${BUILDDIR}" \
OBJ="${BUILDDIR}/regress/" \
PATH="${BUILDDIR}:${PATH}" \
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
make[1]: Entering directory `/home/nchahine/openssh-3.7.1p2/regress'
ssh-keygen -if /home/nchahine/openssh-3.7.1p2/regress/rsa_ssh2.prv | diff -
/home/nchahine/openvcat /home/nchahine/openssh-3.7.1p2/regress/rsa_openssh.prv
> /home/nchahine/openssh-3.7.1p2/regtchmod 600
/home/nchahine/openssh-3.7.1p2/regress//t2.out
ssh-keygen -yf /home/nchahine/openssh-3.7.1p2/regress//t2.out | diff -
/home/nchahine/openssh-3bssh-keygen -ef
/home/nchahine/openssh-3.7.1p2/regress/rsa_openssh.pub
>/home/nchahine/openssh-3bssh-keygen -if
/home/nchahine/openssh-3.7.1p2/regress//rsa_secsh.pub | diff -
/home/nchahine/opbrm -f /home/nchahine/openssh-3.7.1p2/regress/rsa_secsh.pub
ssh-keygen -lf /home/nchahine/openssh-3.7.1p2/regress/rsa_openssh.pub |\
awk '{print $2}' | diff -
/home/nchahine/openssh-3.7.1p2/regress/t4.ok
1c1
< 12:a7:8f:c9:3b:8c:bb:df:62:fc:a1:19:07:5d:2e:fd
---> 3b:dd:44:e9:49:18:84:95:f1:e7:33:6b:9d:93:b1:36
make[1]: *** [t4] Error 1
make[1]: Leaving directory `/home/nchahine/openssh-3.7.1p2/regress'
make: *** [tests] Error 2
sh-2.05#
Any clue??
Nagib
-----Original Message-----
From: Ben Lindstrom [mailto:mouring at etoh.eviladmin.org]
Sent: Tue 11/25/2003 8:39 AM
To: Chahine, Nagib N
Cc: Darren Tucker; openssh-unix-dev at mindrot.org
Subject: RE: Problem running SSH on IBM PPC440 processor, help appreciated
On Tue, 25 Nov 2003, Chahine, Nagib N wrote:
> Hi Darren,
>
> Thanks for your response, however there is no test target in the
> Makefile. There is a logintest: target and when I make it I get the
> following error:
>
Try with an 's'.
make tests
- Ben
Chahine, Nagib N
2003-Nov-25 18:01 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
I ran make tests on my x86 redhat9.0 installation and got a lot further however, after running few tests is stopped here: run test rekey.sh ... run test stderr-data.sh ... make[1]: *** [t-exec] Error 1 make: *** [tests] Error 2 -----Original Message----- From: Ben Lindstrom [mailto:mouring at etoh.eviladmin.org] Sent: Tue 11/25/2003 8:39 AM To: Chahine, Nagib N Cc: Darren Tucker; openssh-unix-dev at mindrot.org Subject: RE: Problem running SSH on IBM PPC440 processor, help appreciated On Tue, 25 Nov 2003, Chahine, Nagib N wrote:> Hi Darren, > > Thanks for your response, however there is no test target in the > Makefile. There is a logintest: target and when I make it I get the > following error: >Try with an 's'. make tests - Ben
Chahine, Nagib N
2003-Nov-25 19:49 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
Sorry, I thought it was a mistype... What is SSL, did I not install something required?? Nagib -----Original Message----- From: Tim Rice [mailto:tim at multitalents.net] Sent: Tuesday, November 25, 2003 10:29 AM To: Chahine, Nagib N Cc: Darren Tucker; openssh-unix-dev at mindrot.org Subject: RE: Problem running SSH on IBM PPC440 processor, help appreciated On Tue, 25 Nov 2003, Chahine, Nagib N wrote:> Hi Darren, > > Thanks for your response, however there is no test target in the Makefile. There is a logintest: target and when I make it I get the following error: > > (cd openbsd-compat && make) > make[1]: Entering directory `/home/nchahine/openssh-3.7.1p2/openbsd-compat'Darren asked you if OpenSSL's "make test" passed not OpenSSH. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net
Chahine, Nagib N
2003-Nov-26 16:30 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
I am running PPC kernel 2.4.21 gcc 2.95.4 from ELDK kit. I will try installing openSSL myself and run the test and see what happen. Thanks Nagib -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tue 11/25/2003 8:09 PM To: Chahine, Nagib N Cc: openssh-unix-dev at mindrot.org Subject: Re: Problem running SSH on IBM PPC440 processor, help appreciated "Chahine, Nagib N" wrote:> > Sorry, I thought it was a mistype... > What is SSL, did I not install something required??OpenSSL is what OpenSSH uses for its crypto functions (libcrypto.[a|so|sl]). It's required to build OpenSSH, so if you didn't install it yourself you probably have it as a system library. It looks like you may be having some kind of crypto problem, and verifying OpenSSL's functionality on your taget platform would be useful in tracking down your problem. BTW, what OS and compiler are you using on your PPC system? (I don't think you specified earlier, but I might have missed it.) -- 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.
Chahine, Nagib N
2003-Nov-26 23:44 UTC
Problem running SSH on IBM PPC440 processor, help appreciated
To David and all who helped thanks.... What I had to do is the following: Install openSSl 0.9.7c and OpenSSH 3.7.1p2 on both my x86 redhat 9 system and my PPC target. Once installed everything works fine. I beleive my problem was openSSL mismatch between the client and server. Thanks Nagib -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Tue 11/25/2003 8:09 PM To: Chahine, Nagib N Cc: openssh-unix-dev at mindrot.org Subject: Re: Problem running SSH on IBM PPC440 processor, help appreciated "Chahine, Nagib N" wrote:> > Sorry, I thought it was a mistype... > What is SSL, did I not install something required??OpenSSL is what OpenSSH uses for its crypto functions (libcrypto.[a|so|sl]). It's required to build OpenSSH, so if you didn't install it yourself you probably have it as a system library. It looks like you may be having some kind of crypto problem, and verifying OpenSSL's functionality on your taget platform would be useful in tracking down your problem. BTW, what OS and compiler are you using on your PPC system? (I don't think you specified earlier, but I might have missed it.) -- 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.