• obfuscated-openssh cann't let me login to server.

    From Hongyi Zhao@110:110/2002 to All on Wed Oct 16 11:32:23 2013
    Hi all,

    I own a account on the ssh server ssh.sshcenter.info, see here http:// www.sshcenter.info/site-sshcenter/pay-ssh-account.php for detail, which supports the obfuscated ssh login method now.

    When I login with the following command, I always failed with the
    following information:

    werner@debian-asus:~$ ssh -Nfx -D 7070 hszhao@ssh.sshcenter.info -p
    60001 -Z key
    ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out

    Why does this happen?

    Regards
    --
    ..: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.

    --- MBSE BBS v1.0.0 (GNU/Linux-i386)
    * Origin: NPO RUSnet InterNetNews site (110:110/2002@linuxnet)
  • From unruh@1:0/0 to All on Wed Oct 16 16:02:11 2013
    On 2013-10-16, Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
    Hi all,

    I own a account on the ssh server ssh.sshcenter.info, see here http:// www.sshcenter.info/site-sshcenter/pay-ssh-account.php for detail, which supports the obfuscated ssh login method now.

    When I login with the following command, I always failed with the
    following information:

    werner@debian-asus:~$ ssh -Nfx -D 7070 hszhao@ssh.sshcenter.info -p
    60001 -Z key
    ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out

    Why does this happen?

    Ask them. This would seem to indicate that they are not listening to
    port 60001 or are very slow to respond.
    Note, are you sure you did not actually want 6001?
    I have no idea what "obfuscated ssh login" means.
    Nor can I read chinese I am afraid.

    Try
    ssh -vvv ...
    to see what your ssh side sent out the other side and is waiting for.





    Regards

    --- MBSE BBS v1.0.0 (GNU/Linux-i386)
    * Origin: The Kofo System II BBS telnet://fido2.kofobb
  • From Hongyi Zhao@110:110/2002 to All on Thu Oct 17 01:47:06 2013
    On Wed, 16 Oct 2013 14:06:45 +0200, ein wrote:

    1. Hostname may be wrong.
    2. SSH port may be wrong.
    3. Something block this connection, for instance a firewall.

    The port and the hostname all are right ;-) I've check them again and
    again. And I can use the http://www.sshcenter.info/site-sshcenter/ software/myentunnel-unicode-3.5.2-obfuscated.zip to login this server
    when I use Windows 7 OS.

    I've use the -v argument to obtain more information, see below for detail:

    -----------
    werner@debian-asus:~$ ssh -l hszhao ssh.sshcenter.info -p 60001 -Z key -v OpenSSH_5.2p1, OpenSSL 0.9.8o 01 Jun 2010
    debug1: Reading configuration data /usr/local/etc/ssh_config
    debug1: Connecting to ssh.sshcenter.info [218.30.64.199] port 60001.
    debug1: connect to address 218.30.64.199 port 60001: Connection timed out
    ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out ----------

    Furthermore, I also checked the file /usr/local/etc/ssh_config, all of
    the content are commented out in this file, and this is the default case.

    See below for detail:

    --------
    werner@debian-asus:~$ cat /usr/local/etc/ssh_config
    # $OpenBSD: ssh_config,v 1.25 2009/02/17 01:28:32 djm Exp $

    # This is the ssh client system-wide configuration file. See
    # ssh_config(5) for more information. This file provides defaults for
    # users, and the values can be changed in per-user configuration files
    # or on the command line.

    # Configuration data is parsed as follows:
    # 1. command line options
    # 2. user-specific file
    # 3. system-wide file
    # Any configuration value is only changed the first time it is set.
    # Thus, host-specific definitions should be at the beginning of the
    # configuration file, and defaults at the end.

    # Site-wide defaults for some commonly used options. For a comprehensive
    # list of available options, their meanings and defaults, please see the
    # ssh_config(5) man page.

    # Host *
    # ForwardAgent no
    # ForwardX11 no
    # RhostsRSAAuthentication no
    # RSAAuthentication yes
    # PasswordAuthentication yes
    # HostbasedAuthentication no
    # GSSAPIAuthentication no
    # GSSAPIDelegateCredentials no
    # BatchMode no
    # CheckHostIP yes
    # AddressFamily any
    # ConnectTimeout 0
    # StrictHostKeyChecking ask
    # IdentityFile ~/.ssh/identity
    # IdentityFile ~/.ssh/id_rsa
    # IdentityFile ~/.ssh/id_dsa
    # Port 22
    # Protocol 2,1
    # Cipher 3des
    # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128- cbc,3des-cbc
    # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
    # EscapeChar ~
    # Tunnel no
    # TunnelDevice any:any
    # PermitLocalCommand no
    # VisualHostKey no
    ---------

    Any hints will be highly appreciated, thanks again.

    Regards
    --
    ..: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.

    --- MBSE BBS v1.0.0 (GNU/Linux-i386)
    * Origin: NPO RUSnet InterNetNews site (110:110/2002@linuxnet)
  • From unruh@1:0/0 to All on Fri Oct 18 08:22:12 2013
    On 2013-10-17, Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
    On Wed, 16 Oct 2013 14:06:45 +0200, ein wrote:

    1. Hostname may be wrong.
    2. SSH port may be wrong.
    3. Something block this connection, for instance a firewall.

    The port and the hostname all are right ;-) I've check them again and again. And I can use the http://www.sshcenter.info/site-sshcenter/ software/myentunnel-unicode-3.5.2-obfuscated.zip to login this server
    when I use Windows 7 OS.

    I've use the -v argument to obtain more information, see below for detail:

    -----------
    werner@debian-asus:~$ ssh -l hszhao ssh.sshcenter.info -p 60001 -Z key -v OpenSSH_5.2p1, OpenSSL 0.9.8o 01 Jun 2010
    debug1: Reading configuration data /usr/local/etc/ssh_config
    debug1: Connecting to ssh.sshcenter.info [218.30.64.199] port 60001.
    debug1: connect to address 218.30.64.199 port 60001: Connection timed out ssh: connect to host ssh.sshcenter.info port 60001: Connection timed out ----------

    Well that tells you that the other side is not responsding. You have to
    take it up with them. Nothing you can do.
    What is it wirth 60001 port?


    Furthermore, I also checked the file /usr/local/etc/ssh_config, all of
    the content are commented out in this file, and this is the default case.

    See below for detail:

    There are none. All lines are comments. None do anything.


    --------
    werner@debian-asus:~$ cat /usr/local/etc/ssh_config
    # $OpenBSD: ssh_config,v 1.25 2009/02/17 01:28:32 djm Exp $

    # This is the ssh client system-wide configuration file. See
    # ssh_config(5) for more information. This file provides defaults for
    # users, and the values can be changed in per-user configuration files
    # or on the command line.

    # Configuration data is parsed as follows:
    # 1. command line options
    # 2. user-specific file
    # 3. system-wide file
    # Any configuration value is only changed the first time it is set.
    # Thus, host-specific definitions should be at the beginning of the
    # configuration file, and defaults at the end.

    # Site-wide defaults for some commonly used options. For a comprehensive
    # list of available options, their meanings and defaults, please see the
    # ssh_config(5) man page.

    # Host *
    # ForwardAgent no
    # ForwardX11 no
    # RhostsRSAAuthentication no
    # RSAAuthentication yes
    # PasswordAuthentication yes
    # HostbasedAuthentication no
    # GSSAPIAuthentication no
    # GSSAPIDelegateCredentials no
    # BatchMode no
    # CheckHostIP yes
    # AddressFamily any
    # ConnectTimeout 0
    # StrictHostKeyChecking ask
    # IdentityFile ~/.ssh/identity
    # IdentityFile ~/.ssh/id_rsa
    # IdentityFile ~/.ssh/id_dsa
    # Port 22
    # Protocol 2,1
    # Cipher 3des
    # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128- cbc,3des-cbc
    # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
    # EscapeChar ~
    # Tunnel no
    # TunnelDevice any:any
    # PermitLocalCommand no
    # VisualHostKey no
    ---------

    Any hints will be highly appreciated, thanks again.

    Regards

    --- MBSE BBS v1.0.0 (GNU/Linux-i386)
    * Origin: The Kofo System II BBS telnet://fido2.kofobb
  • From Hongyi Zhao@110:110/2002 to All on Sat Nov 2 06:55:13 2013
    On Mon, 21 Oct 2013 04:21:07 +0200, ein wrote:

    According to 'nslookup ssh.sshcenter.inf':

    ;; Truncated, retrying in TCP mode.
    Server: 127.0.0.1 Address: 127.0.0.1#53

    Non-authoritative answer:
    ssh.sshcenter.info canonical name = c-ssh.luozhucheng.info.
    Name: c-ssh.luozhucheng.info Address: 108.61.74.44 Name: c-ssh.luozhucheng.info Address: 142.4.60.109 Name:
    c-ssh.luozhucheng.info Address: 162.210.39.138 Name:
    c-ssh.luozhucheng.info Address: 162.218.93.91 Name:
    c-ssh.luozhucheng.info Address: 162.220.218.146 Name: c-ssh.luozhucheng.info Address: 173.252.246.216 Name: c-ssh.luozhucheng.info Address: 173.254.227.21 Name:
    c-ssh.luozhucheng.info Address: 184.95.43.34 Name:
    c-ssh.luozhucheng.info Address: 192.30.35.196 Name:
    c-ssh.luozhucheng.info Address: 198.23.227.195 Name:
    c-ssh.luozhucheng.info Address: 198.56.129.15 Name:
    c-ssh.luozhucheng.info Address: 198.98.103.195 Name:
    c-ssh.luozhucheng.info Address: 198.199.101.80 Name:
    c-ssh.luozhucheng.info Address: 199.68.199.229 Name:
    c-ssh.luozhucheng.info Address: 199.91.71.205 Name:
    c-ssh.luozhucheng.info Address: 199.119.224.224 Name: c-ssh.luozhucheng.info Address: 199.231.227.191 Name: c-ssh.luozhucheng.info Address: 209.141.63.131 Name:
    c-ssh.luozhucheng.info Address: 216.24.199.57 Name:
    c-ssh.luozhucheng.info Address: 216.158.84.79 Name:
    c-ssh.luozhucheng.info Address: 23.90.4.123 Name:
    c-ssh.luozhucheng.info Address: 69.163.34.77 Name:
    c-ssh.luozhucheng.info Address: 69.197.147.91 Name:
    c-ssh.luozhucheng.info Address: 69.197.147.92 Name:
    c-ssh.luozhucheng.info Address: 74.82.164.28

    According your above results, you can find all of the ip addreses that
    binded with the FQDN ssh.sshcenter.info. But in my case, I only can find
    one IP of them:

    -------
    werner@debian-asus:~$ nslookup ssh.sshcenter.info
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    Non-authoritative answer:
    Name: ssh.sshcenter.info
    Address: 216.24.199.57
    ----------

    Why does this happen?

    Regards
    --
    ..: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: NPO RUSnet InterNetNews site (110:110/2002@linuxnet)
  • From Pascal Hambourg@110:110/2002 to All on Sat Nov 2 09:15:28 2013
    Reply-To: pascal.news@plouf.fr.eu.org

    Hello,

    Hongyi Zhao a ‚crit :

    According your above results, you can find all of the ip addreses that binded with the FQDN ssh.sshcenter.info. But in my case, I only can find one IP of them:

    -------
    werner@debian-asus:~$ nslookup ssh.sshcenter.info
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    Non-authoritative answer:
    Name: ssh.sshcenter.info
    Address: 216.24.199.57
    ----------

    Why does this happen?

    Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or
    lies. It does not even mention that ssh.sshcenter.info is a CNAME
    (alias). Can't you use another one ?

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: Plouf ! (110:110/2002@linuxnet)
  • From Hongyi Zhao@110:110/2002 to All on Sun Nov 3 03:15:26 2013
    On Sat, 02 Nov 2013 10:15:28 +0100, Pascal Hambourg wrote:

    Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or lies. It does not even mention that ssh.sshcenter.info is a CNAME
    (alias). Can't you use another one ?

    I don't know how to find the recursive DNS server for my case, see the following output on my Debian box:

    ----------
    werner@debian-asus:~$ sudo ifconfig
    eth0 Link encap:Ethernet HWaddr c8:60:00:df:24:23
    inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::ca60:ff:fedf:2423/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:34079 errors:0 dropped:0 overruns:0 frame:0
    TX packets:32438 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:25156142 (23.9 MiB) TX bytes:4868917 (4.6 MiB)
    Interrupt:20 Memory:f7300000-f7320000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:85 errors:0 dropped:0 overruns:0 frame:0
    TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:346591 (338.4 KiB) TX bytes:346591 (338.4 KiB)
    -----------

    Regards

    --
    ..: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: NPO RUSnet InterNetNews site (110:110/2002@linuxnet)
  • From Pascal Hambourg@110:110/2002 to All on Sun Nov 3 07:31:41 2013
    Reply-To: pascal.news@plouf.fr.eu.org

    Hongyi Zhao a ‚crit :
    On Sat, 02 Nov 2013 10:15:28 +0100, Pascal Hambourg wrote:

    Your recursive DNS server 192.168.0.1 (or its upstream DNS) is broken or
    lies. It does not even mention that ssh.sshcenter.info is a CNAME
    (alias). Can't you use another one ?

    I don't know how to find the recursive DNS server for my case

    The nameserver addresses are defined in /etc/resolv.conf. However you
    can test a different nameserver with nslookup,dig,host without modifying
    the file. E.g. if you want to test one of Google's open DNS servers :

    $ nslookup ssh.sshcenter.info 8.8.8.8

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: Plouf ! (110:110/2002@linuxnet)
  • From Hongyi Zhao@110:110/2002 to All on Mon Nov 4 02:09:06 2013
    On Sun, 03 Nov 2013 08:31:41 +0100, Pascal Hambourg wrote:

    $ nslookup ssh.sshcenter.info 8.8.8.8

    Good, thanks.

    Regards
    --
    ..: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.

    --- MBSE BBS v1.0.1 (GNU/Linux-i386)
    * Origin: NPO RUSnet InterNetNews site (110:110/2002@linuxnet)