DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2009-01-10 18:48:47

duorah
New member
Registered: 2009-01-08
Posts: 3

ssh exits on DNS323.

I just got ffp working and trying to shift to ssh. However, ssh is exiting. Here are the logs from the two side:

client session:
OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.15 [192.168.1.15] port 22.
debug1: Connection established.
debug1: identity file /Users/jun/.ssh/identity type -1
debug1: identity file /Users/jun/.ssh/id_rsa type -1
debug1: identity file /Users/jun/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1
debug1: match: OpenSSH_5.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '192.168.1.15' is known and matches the RSA host key.
debug1: Found key in /Users/jun/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/jun/.ssh/identity
debug1: Trying private key: /Users/jun/.ssh/id_rsa
debug1: Trying private key: /Users/jun/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
root@192.168.1.15's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
usage: ssh [-1246AaCfgKkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-e escape_char] [-F configfile]
           [-i identity_file] [-L [bind_address:]port:host:hostport]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-R [bind_address:]port:host:hostport] [-S ctl_path]
           [-w local_tun[:remote_tun]] [user@]hostname [command]
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to 192.168.1.15 closed.
Transferred: sent 1728, received 2504 bytes, in 0.0 seconds
Bytes per second: sent 51983.9, received 75328.6
debug1: Exit status 255


Server side:
Jan 10 08:38:15 DLINK auth.info sshd[19981]: Connection from 192.168.1.64 port 56460
Jan 10 08:38:16 DLINK auth.info sshd[19981]: Failed none for root from 192.168.1.64 port 56460 ssh2
Jan 10 08:38:36 DLINK user.warn kernel:
Jan 10 08:38:36 DLINK user.warn kernel: #######################################
Jan 10 08:38:36 DLINK user.warn kernel: #              HD1 awake now !        #
Jan 10 08:38:36 DLINK user.warn kernel: #######################################
Jan 10 08:38:36 DLINK user.warn kernel:
Jan 10 08:38:36 DLINK user.warn kernel: #######################################
Jan 10 08:38:36 DLINK user.warn kernel: #              HD0 awake now !        #
Jan 10 08:38:36 DLINK user.warn kernel: #######################################
Jan 10 08:38:48 DLINK auth.info sshd[19981]: Accepted password for root from 192.168.1.64 port 56460 ssh2
Jan 10 08:38:48 DLINK auth.info sshd[19981]: Connection closed by 192.168.1.64
Jan 10 08:38:48 DLINK auth.info sshd[19981]: Transferred: sent 2504, received 1728 bytes
Jan 10 08:38:48 DLINK auth.info sshd[19981]: Closing connection to 192.168.1.64 port 56460

Due to the second line (Failed none) I tried to specify the cipher with a -c blowfish, but same result.

Thanks

Offline

 

#2 2009-01-10 19:02:18

duorah
New member
Registered: 2009-01-08
Posts: 3

Re: ssh exits on DNS323.

On seconds thought, I added a user to the DNS and tried to log in as that user.
That seems to work but the session hangs without a prompt.

debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.15 [192.168.1.15] port 22.
debug1: Connection established.
debug1: identity file /Users/jun/.ssh/identity type -1
debug1: identity file /Users/jun/.ssh/id_rsa type -1
debug1: identity file /Users/jun/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1
debug1: match: OpenSSH_5.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '192.168.1.15' is known and matches the RSA host key.
debug1: Found key in /Users/jun/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/jun/.ssh/identity
debug1: Trying private key: /Users/jun/.ssh/id_rsa
debug1: Trying private key: /Users/jun/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
jun@192.168.1.15's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.


BusyBox v1.00-pre1 (2008.09.02-11:43+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.


Server:
Jan 10 08:56:58 DLINK auth.info sshd[20570]: Connection from 192.168.1.64 port 56549
Jan 10 08:56:59 DLINK auth.info sshd[20570]: Failed none for jun from 192.168.1.64 port 56549 ssh2
Jan 10 08:57:02 DLINK auth.info sshd[20570]: Accepted password for jun from 192.168.1.64 port 56549 ssh2
Jan 10 08:57:02 DLINK auth.info sshd[20570]: User child is on pid 20572

The only difference seems to be that the non root user was created a chid with pid, but in root case the session was closed. I checked the ssh_config, and altough I was still using the defaults, uncommented the line for AllowRootLogin Yes. Still no go.

Offline

 

#3 2009-01-10 21:32:59

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: ssh exits on DNS323.

Offline

 

#4 2009-01-11 06:39:48

duorah
New member
Registered: 2009-01-08
Posts: 3

Re: ssh exits on DNS323.

Thanks. Apparently, I missed some parts of the text and did not set the shell for user,
also overwrite coreutil with ffp-base etc etc.

THis time, it is working much better. smile

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB