Bug#312887: ssh-krb5: Corrupted MAC on input

2005-06-10 Thread Dave Love
Package: ssh-krb5
Version: 3.8.1p1-7
Severity: normal

I just had a session disconnected with

  Disconnecting: Corrupted MAC on input.

This was between two sparcs running ssh-krb5 under sarge, with firefox
running from the remote end.

Is this likely to be an ssh error or something to do with networking,
for instance?  Any ideas for diagnosis if it happens again?


-- System Information:
Debian Release: 3.1
Architecture: sparc (sparc64)
Kernel: Linux 2.4.26-sparc64
Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages ssh-krb5 depends on:
ii  adduser 3.63 Add and remove users and groups
ii  debconf 1.4.30.13Debian configuration management sy
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libcomerr2  1.37-2sarge1 common error description library
ii  libkrb531.3.6-2  MIT Kerberos runtime libraries
ii  libpam-runtime  0.76-22  Runtime support for the PAM librar
ii  libpam0g0.76-22  Pluggable Authentication Modules l
ii  libssl0.9.7 0.9.7e-3 SSL shared libraries
ii  libwrap07.6.dbs-8Wietse Venema's TCP wrappers libra
ii  zlib1g  1:1.2.2-4compression library - runtime

-- debconf information:
* ssh/privsep_tell:
  ssh/insecure_rshd:
  ssh/privsep_ask: true
* ssh/ssh2_keys_merged:
* ssh/user_environment_tell:
* ssh/forward_warning:
  ssh/insecure_telnetd:
* ssh/new_config: false
* ssh/use_old_init_script: true
* ssh/protocol2_only: false
  ssh/encrypted_host_key_but_no_keygen:
* ssh/run_sshd: true
* ssh/SUID_client: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#312887: ssh-krb5: Corrupted MAC on input

2005-06-10 Thread Russ Allbery
Dave Love [EMAIL PROTECTED] writes:

 Package: ssh-krb5
 Version: 3.8.1p1-7
 Severity: normal

 I just had a session disconnected with

   Disconnecting: Corrupted MAC on input.

 This was between two sparcs running ssh-krb5 under sarge, with firefox
 running from the remote end.

 Is this likely to be an ssh error or something to do with networking,
 for instance?  Any ideas for diagnosis if it happens again?

This happens fairly regularly to me on one system (x86).  I have been told
that it's common with bad NICs to get bit corruption inside the NIC before
the kernel gets the packets.  If it happens regularly on some systems and
not on others, I'd be inclined to suspect that explanation.

-- 
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]