Re: "Corrupted MAC on input"
From: Eloi Granado (eloi.granado_at_millorsoft.net)
Date: 01/03/04
- Previous message: Matt Howard: "Re: "Corrupted MAC on input""
- In reply to: Matt Howard: "Re: "Corrupted MAC on input""
- Next in thread: Matt Howard: "Re: "Corrupted MAC on input""
- Reply: Matt Howard: "Re: "Corrupted MAC on input""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: secureshell@securityfocus.com Date: Sat, 3 Jan 2004 09:48:36 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
But then it wouldn't appear specifically after transmitting 1GB by ssh,
but randomly and probably early.
On Saturday 03 January 2004 02:12, Matt Howard wrote:
> The MAC in a ssh packet is similar to a CRC checksum. I usually see
> errors like this crop up on systems with corruption problems in the NIC
> buffers. The packet was received OK and checksummed OK, but when the OS
> reads the data out for it's own use, the data is corrupt. If you're
> using an Intel 10/100 nic, I would try switching to the other network
> driver ( eepro100 vs. e100 ) I've had this issue with Intel's driver,
> specifically. Anyway, this is not a definitive answer, just what I
> surmised from investigation. I'd like to see an update on the issue, to
> see if we find a common thread.
- --
- -----------------------------------------------------
Eloi Granado (eloi.granado@millorsoft.net)
PGP Key: http://eloi.millorsoft.es/pgp-publickey.asc
- -----------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/9oHpewfs1FO2wi0RAnsyAKCq2LHJnou8/dXC4nBKB/rXV2NZOwCgycUd
CLLp0ZfnAlXfZ0jClspgRIY=
=exHG
-----END PGP SIGNATURE-----
- Previous message: Matt Howard: "Re: "Corrupted MAC on input""
- In reply to: Matt Howard: "Re: "Corrupted MAC on input""
- Next in thread: Matt Howard: "Re: "Corrupted MAC on input""
- Reply: Matt Howard: "Re: "Corrupted MAC on input""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]