Re: ssh corrupt packets with aes encryption

2013-05-13 Thread Joe Pfeiffer
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. 2) Boot from livecd, if possible, see if openssh

Re: ssh corrupt packets with aes encryption

2013-05-13 Thread recoverym4n
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

Re: ssh corrupt packets with aes encryption

2013-05-13 Thread Joe Pfeiffer
recovery...@gmail.com writes: Can you provide a result of tcpdump -nn -s0 -i lo tcp port 22 ? I don't have any experience with tcpdump, so I'm just blindly following instructions here -- let me know if you need more! tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

Re: ssh corrupt packets with aes encryption

2013-05-13 Thread recoverym4n
On Mon, 13 May 2013 13:05:41 -0600 Joe Pfeiffer pfeif...@cs.nmsu.edu wrote: recovery...@gmail.com writes: Can you provide a result of tcpdump -nn -s0 -i lo tcp port 22 ? I don't have any experience with tcpdump, so I'm just blindly following instructions here -- let me know if you

ssh corrupt packets with aes encryption

2013-05-11 Thread Joe Pfeiffer
On a fresh install, I can neither ssh in to nor out of one of my machines using aes encryption -- I get the error lcct@projections:~$ ssh localhost Bad packet length 3783539029. Disconnecting: Packet corrupt If I delete the known_hosts file turn on some debugging, I get lcct@projections:~$ ssh

Re: ssh corrupt packets with aes encryption

2013-05-11 Thread recoverym4n
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. 2) Boot from livecd, if possible, see if openssh works there. 3) If possible, swap