Re: Disconnecting: Corrupted MAC on input.

From: weiser, olaf (olaf.weiser_at_t-systems.com)
Date: 05/06/05

  • Next message: CP Lim: "Binding ssh to a loopback address" 
    Date: Fri, 06 May 2005 07:54:35 +0200
To: David Ho <DavidHo@nanometrics.ca>

    Hallo ,

    do you have any network connection / IP adress configured on this host?
     if, please check, if there is an opportunity to let the sshd know, to
    use this interface
    (sshd conf or smth like that....)

    after that, checkt the ouput, especially the line "Bind to port....."
    good luck

    David Ho wrote:

    >Hi all,
    >
    >I am compiling sshd version OpenSSH_4.0p1 natively on an embbeded ppc for
    >secure access to the unit. I have managed to build the executables with
    >PAM support on this measly 60MHz, 128MB MPC8xx.
    >
    >However when I try to connect to the daemon from a Linux box this is the
    >result I got at the server, debug enabled.
    >
    >Any help is much appreciated.
    >
    >Thanks, David
    >
    >
    >bash-2.05b# /usr/local/sbin/sshd -d
    >debug1: sshd version OpenSSH_4.0p1
    >debug1: private host key: #0 type 0 RSA1
    >debug1: read PEM private key done: type RSA
    >debug1: private host key: #1 type 1 RSA
    >debug1: read PEM private key done: type DSA
    >debug1: private host key: #2 type 2 DSA
    >debug1: rexec_argv[0]='/usr/local/sbin/sshd'
    >debug1: rexec_argv[1]='-d'
    >socket: Address family not supported by protocol
    >debug1: Bind to port 22 on 0.0.0.0.
    >Server listening on 0.0.0.0 port 22.
    >Generating 768 bit RSA key.
    >RSA key generation complete.
    >debug1: Server will not fork when running in debugging mode.
    >debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
    >debug1: inetd sockets after dupping: 3, 3
    >Connection from 199.71.138.9 port 34673
    >debug1: Client protocol version 2.0; client software version OpenSSH_3.5p1
    >debug1: match: OpenSSH_3.5p1 pat OpenSSH_3.*
    >debug1: Enabling compatibility mode for protocol 2.0
    >debug1: Local version string SSH-1.99-OpenSSH_4.0
    >debug1: permanently_set_uid: 95/95
    >debug1: list_hostkey_types: ssh-rsa,ssh-dss
    >debug1: SSH2_MSG_KEXINIT sent
    >debug1: SSH2_MSG_KEXINIT received
    >debug1: kex: client->server aes128-cbc hmac-md5 none
    >debug1: kex: server->client aes128-cbc hmac-md5 none
    >debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
    >debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
    >debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
    >debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
    >debug1: SSH2_MSG_NEWKEYS sent
    >debug1: expecting SSH2_MSG_NEWKEYS
    >debug1: SSH2_MSG_NEWKEYS received
    >debug1: KEX done
    >Disconnecting: Corrupted MAC on input.
    >debug1: do_cleanup
    >debug1: do_cleanup
    >
    >

  • Next message: CP Lim: "Binding ssh to a loopback address"

    Relevant Pages

    • SOLVED: Newbie: SSH fails to connect; gives strange error message
      ... >> You're attempting to run a debug SSHD, but there's still a copy running ... >> on another port and try to connect to that port from the client. ... > debug1: Connection established. ... > RSA key generation complete. ...
      (comp.security.ssh)
    • Re: McAfee and CygWin SSH
      ... Try it with sshd -d and see what it says -- perhaps something is ... debug1: sshd version OpenSSH_4.3p2 ... debug1: read PEM private key done: type RSA ...
      (comp.security.ssh)
    • Re: Cant login to an OS X box using ssh
      ... using sshd -d which seems to be more helpful than ssh -d5 or any level ... verbose mode on the client side. ... debug1: read PEM private key done: type RSA ... SSH Secure Shell ...
      (comp.security.ssh)
    • Re: Help setting up sshd, please
      ... I'm trying to get sshd working on an embryonic Gentoo installation. ... I've run sshd as sshd -d, which puts debugging info onto the screen. ... debug1: userauth-request for user root service ssh-connection method ... then you're on the installation media's kernel still. ...
      (comp.os.linux.setup)
    • sftp only works for root
      ... I can only get sftp to work for root. ... If I sftp using a non-root user account, I get the following from sshd -d: ... debug1: Received SIGCHLD. ...
      (comp.security.ssh)