On Mon, 13 May 2013 08:48:44 -0600 Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote:
> recovery...@gmail.com writes: > > > On Sat, 11 May 2013 09:41:49 -0600 > > Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote: > > > >> So... any idea where to go next? > > > > Hi. > > > > 1) Try to unload kernel module aes_x86_64 and it's dependants, restart > > sshd, try once more. Ok. My idea was that in-kernel implementation of Intel's in-CPU AES instructions corrupts sshd connection. Can you provide a result of tcpdump -nn -s0 -i lo tcp port 22 ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130513214920.b4cb40bd6f4e63f13fd10...@gmail.com
