>From my note:
> I've checked the md5 checksums for all the files in the openssh and
> openssl packages, as well as all the shared libraries the sshd binary
> uses. 

So, not that I can tell.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Rick Troth
Sent: Saturday, September 23, 2006 3:38 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OpenSSH Oddity

Target system has different run-time libs?

-- R;

On Sat, 23 Sep 2006, Post, Mark K wrote:

> I'm having a very strange problem show up with OpenSSH 4.3p1.  On the
> development system where I built it, it works fine.  When I ship the
> binary package to another Linux guest on the same z/VM system, it
> doesn't work.  When I try to ssh into the system, the client gets a
> "Connection closed by 192.168.0.20" message, without even being
prompted
> for a password.  The sshd daemon on the other system throws off this
> error in the kernel ring buffer (but keeps on running):
> User process fault: interruption code 0x4
> failing address: 40016000
> CPU:    0    Not tainted
> Process sshd (pid: 13181, task: 0152c000, ksp: 0152dd00)
> User PSW : 070dc000 c0006318
> User GPRS: ffffffff 40017738 00010dd0 00000000
>            00000000 ffffffff 7fffcfa8 40016f3c
>            00000000 00000000 40016f3c 7fffcf68
>            40017000 c0006164 c00064b2 7fffcf48
> User ACRS: 40010870 00000000 00000000 00000000
>            00000000 00000000 00000000 00000000
>            00000000 00000000 00000000 00000000
>            00000000 00000000 00000000 00000000
> User Code: 50 00 70 00 a7 f4 ff ed 58 80 b0 d4 58 90 d0 40 58 20 80 00
>
>
> I've checked the md5 checksums for all the files in the openssh and
> openssl packages, as well as all the shared libraries the sshd binary
> uses.  They all match on both systems.  Even if I build the binary on
> the target system, I get the same results.  I'm at a loss to explain
why
> it works fine on one system, but not others.  Anyone have any ideas
> where to look further?
>
>
> Thanks,
>
> Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to