-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2007-08-06 a las 11:01 +0200, Kendy Kutzner escribió:
On 2007-07-12T15:58:24+0200, Carlos E. R. wrote:
The Wednesday 2007-07-11 at 14:44 +0200, su.secu@ wrote:
After a few Bytes I got the message on the receiver: 'Disconnecting: Corrupted MAC on input' and on the sender 'received disconnect from xxx.xxx.xxx.xxx: 2: Corrupted MAC on input'. The receiver host is a SuSE 10.2 and the sender host is a SuSE 10.1, both host with all updates. When I search in the net I found the problem in context with the kernel and the nic's.
I fail to see what your problem has to do with "security".
Note that scp (or better the ssh underneath) complains about a corrupt Message Authentication Code, not about a bad Medium Access Control address. (MAC != MAC)
Ah... I see. The error message should be more clear, not used a confusing acronym. But then, you should have posted this to the list, not to me in private. I'm answering to the list, leaving your full text, in the hope the OP sees it.
The message authentication code is responsible to ensure the integrity of the data stream, and as such it is security related.
Reasons for the above message can be an active attacker trying to tamper with your connection or data errors not detected by other mechanisms.
Kendy
- -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGuGBwtTMYHG2NR9URAu2FAJwMR7PKlPmQszrvT44ubat+oLiulACfQWvy x3StzGFLsz9trnp6E9b0wUA= =Qs1j -----END PGP SIGNATURE-----