On Fri, Feb 07, 2003 at 07:09:49PM +0100, Dag-Erling Smorgrav wrote:
> In any case, the message indicates data corruption in the TCP
> connection which has gone undetected by the NIC and the network stack.
> It's a very unlikely occurrence, but not impossible.
Does this imply hardware fail
On Fri, Feb 07, 2003 at 06:50:42PM +0100, Dag-Erling Smorgrav wrote:
> Dave Uhring <[EMAIL PROTECTED]> writes:
> > Before I replaced the binaries with those from the openssh-3.5p1 package and
> > disabled PAM this was what my machine reported:
> >
> > Feb 6 06:59:43 willy sshd[139]: pam_start: ma
Dave Uhring <[EMAIL PROTECTED]> writes:
> Before I replaced the binaries with those from the openssh-3.5p1 package and
> disabled PAM this was what my machine reported:
>
> Feb 6 06:59:43 willy sshd[139]: pam_start: malloc failed for pam_conv
> Feb 6 06:59:43 willy sshd[139]: fatal: PAM: initial
On Fri February 7 2003 04:37 pm, Dave Uhring wrote:
> On Friday 07 February 2003 08:55 am, Dag-Erling Smorgrav wrote:
> > Mark Nipper <[EMAIL PROTECTED]> writes:
> > > Anyway, any ideas on the SSH error?
> >
> > Sure, if you tell me what the error is.
>
> Before I replaced the binaries with those f
