SEO

I am running a fresh installation of Slackware 9.0 in a Pentium 166, 32MB
RAM, 8GB box. I moved all of my web content and other files from another
Pentium 166 but with 64MB RAM that was running Slackware 8.0.

I have a Windows machine that I use as my real computer and I transfer all
of my web content to the linux server via SSH. When I tried sending some
files to the new Slackware 9.0 server everything was fine until the que got
to a large (65MB) file. The SSH client crashed after about 5 or 6 MB at
500-650 kBs. The error said

Server responded"Corrupted MAC on input"

A protocol error was detected. This usually indicates a bug in the SSH
application(either client or server).

I downloaded the newest version of SSH from SSH.com and got the exact same
error after uninstalling and reinstalling the new client.


Is my P 166/ 16MB RAM machine just too slow to handle the transfer or is
there a bug or some incompatability between my client and server?

Here are some details.

SSH Client
3.2.5(Build280) from SSH.com
non-commercial version w/o PKI and PKCS#11

SSH Server
OpenSSH_3.5p1

Files are large binaries 65MB+
Smaller binaries (<10MB) upload and download fine.

Thanks

ihk419 wrote:
> I am running a fresh installation of Slackware 9.0 in a Pentium 166, 32MB
> RAM, 8GB box. I moved all of my web content and other files from another
> Pentium 166 but with 64MB RAM that was running Slackware 8.0.
>
> I have a Windows machine that I use as my real computer and I transfer all
> of my web content to the linux server via SSH. When I tried sending some
> files to the new Slackware 9.0 server everything was fine until the que got
> to a large (65MB) file. The SSH client crashed after about 5 or 6 MB at
> 500-650 kBs. The error said
>
> Server responded"Corrupted MAC on input"
>
> A protocol error was detected. This usually indicates a bug in the SSH
> application(either client or server).
>
> I downloaded the newest version of SSH from SSH.com and got the exact same
> error after uninstalling and reinstalling the new client.
>
>
> Is my P 166/ 16MB RAM machine just too slow to handle the transfer or is
> there a bug or some incompatability between my client and server?
>
> Here are some details.
>
> SSH Client
> 3.2.5(Build280) from SSH.com
> non-commercial version w/o PKI and PKCS#11
>
> SSH Server
> OpenSSH_3.5p1

I don't know what the problem is but there has been several
openSSH security updates lately. It is now at version 3.7.1p2
which is in the patches directory at one of the mirror sites.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 5:53, 1 user, load average: 0.32, 0.47, 0.37

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Sep 26, 2003 at 06:10:37AM +0000, ihk419 wrote:

> I am running a fresh installation of Slackware 9.0 in a Pentium 166, 32MB
> RAM, 8GB box. I moved all of my web content and other files from another
> Pentium 166 but with 64MB RAM that was running Slackware 8.0.
>
> I have a Windows machine that I use as my real computer and I transfer all
> of my web content to the linux server via SSH. When I tried sending some
> files to the new Slackware 9.0 server everything was fine until the que got
> to a large (65MB) file. The SSH client crashed after about 5 or 6 MB at
> 500-650 kBs. The error said
>
> Server responded"Corrupted MAC on input"

try the following;

transfer the same file from one linux server to the other.
see if that goes without any problems.

then on the windows machine, download pscp.exe (from the putty
download page) and use that to transfer that file again from the
wintendo machine to the linux server.

does it generate the same error ? or do things work properly now ?


Jurgen.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/c9wn1ucXIiwNwbURApMoAKDgQlTaxhqu5yMtEOmJ71zS84h/IQCgsqSK
EBKVMaSJvIZys4pApR6lujY=
=riJu
-----END PGP SIGNATURE-----