ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: February 20, 2019, 10:02:16 am 
Started by dbonine - Last post by jaredh
Did you get an answer?

 22 
 on: February 19, 2019, 03:26:06 pm 
Started by jaredh - Last post by jaredh
See this link:

https://www.ssh.com/ssh/putty/putty-manuals/0.68/Chapter4.html

Section 4.27.13 ‘ONLY SUPPORTS PRE-RFC4419 SSH-2 DH GEX’


 23 
 on: February 19, 2019, 03:10:14 pm 
Started by jaredh - Last post by jaredh
I know what the issue is:

From the 6.9 OpenSSH patch notes:

 * ssh(1), sshd(8): deprecate legacy SSH2_MSG_KEX_DH_GEX_REQUEST_OLD
   message and do not try to use it against some 3rd-party SSH
   implementations that use it (older PuTTY, WinSCP).

Dejawin is using a PuTTY version that sends this message to the host.  Here is a log from a server that works:

Feb 19 14:58:13 uatinf2 sshd[5808]: Connection from 192.168.33.18 port 54527 on 192.168.7.15 port 22
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: Client protocol version 2.0; client software version PuTTY-Local: Apr  4 2011 16:23:55
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: no match: PuTTY-Local: Apr  4 2011 16:23:55
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: Enabling compatibility mode for protocol 2.0
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: permanently_set_uid: 71/65 [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_KEXINIT received [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: kex: client->server aes256-cbc hmac-sha1 none [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: kex: server->client aes256-cbc hmac-sha1 none [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_NEWKEYS sent [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: expecting SSH2_MSG_NEWKEYS [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: SSH2_MSG_NEWKEYS received [preauth]
Feb 19 14:58:13 uatinf2 sshd[5808]: debug1: KEX done [preauth]
Feb 19 14:58:18 uatinf2 sshd[5808]: debug1: userauth-request for user jheath service ssh-connection method none [preauth]
Feb 19 14:58:18 uatinf2 sshd[5808]: debug1: attempt 0 failures 0 [preauth]

I suspect they are ignoring this message from the client and the negotiation is busted at that point but the connection doesn't die until it tries to tie to a TTY.



 24 
 on: February 19, 2019, 11:26:56 am 
Started by jaredh - Last post by jaredh
This is a SLES 12 SP4 server running OpenSSH_7.2p2, OpenSSL 1.0.2p-fips  14 Aug 2018

Initially, it would not do anything except close.  That led me to the KexAlgorithim changes listed in the forum here.  Changing those and restarting gets sshd to talk to the client and offer up a password prompt.

Once user/passwd are entered, it goes through as expected doing PAM auth but the window simply goes away when the sshd server starts to initialize the TTY.  Here is an example logfile:

Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: Client protocol version 2.0; client software version PuTTY-Local: Apr  4 2011 16:23:55
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: no match: PuTTY-Local: Apr  4 2011 16:23:55
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: Enabling compatibility mode for protocol 2.0
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: Local version string SSH-2.0-OpenSSH_7.2
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: permanently_set_uid: 71/65 [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: list_hostkey_types: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: SSH2_MSG_KEXINIT received [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: algorithm: diffie-hellman-group1-sha1 [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: host key algorithm: ssh-rsa [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: client->server cipher: aes256-cbc MAC: hmac-sha1 compression: none [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: server->client cipher: aes256-cbc MAC: hmac-sha1 compression: none [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: diffie-hellman-group1-sha1 need=32 dh_need=32 [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: kex: diffie-hellman-group1-sha1 need=32 dh_need=32 [preauth]
Feb 19 11:07:18 uatappx2 sshd[39680]: debug1: expecting SSH2_MSG_KEXDH_INIT [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: rekey after 4294967296 blocks [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: SSH2_MSG_NEWKEYS sent [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: expecting SSH2_MSG_NEWKEYS [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: SSH2_MSG_NEWKEYS received [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: rekey after 4294967296 blocks [preauth]
Feb 19 11:07:19 uatappx2 sshd[39680]: debug1: KEX done [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: userauth-request for user lsmith service ssh-connection method none [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: attempt 0 failures 0 [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: PAM: initializing for "lsmith"
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: PAM: setting PAM_RHOST to "192.168.33.18"
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: PAM: setting PAM_TTY to "ssh"
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: userauth-request for user lsmith service ssh-connection method keyboard-interactive [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: attempt 1 failures 0 [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: keyboard-interactive devs  [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: auth2_challenge: user=lsmith devs= [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: kbdint_alloc: devices 'pam' [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: auth2_challenge_start: trying authentication method 'pam' [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: Postponed keyboard-interactive for lsmith from 192.168.33.18 port 51352 ssh2 [preauth]
Feb 19 11:07:24 uatappx2 sshd[39683]: debug1: do_pam_account: called
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: PAM: num PAM env strings 0
Feb 19 11:07:24 uatappx2 sshd[39680]: Postponed keyboard-interactive/pam for lsmith from 192.168.33.18 port 51352 ssh2 [preauth]
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: do_pam_account: called
Feb 19 11:07:24 uatappx2 sshd[39680]: Accepted keyboard-interactive/pam for lsmith from 192.168.33.18 port 51352 ssh2
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: monitor_child_preauth: lsmith has been authenticated by privileged process
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: monitor_read_log: child log fd closed
Feb 19 11:07:24 uatappx2 sshd[39680]: debug1: PAM: establishing credentials
Feb 19 11:07:24 uatappx2 systemd[1]: Created slice User Slice of lsmith.
Feb 19 11:07:24 uatappx2 systemd[1]: Starting User Manager for UID 2017...
Feb 19 11:07:24 uatappx2 systemd-logind[1498]: New session 227 of user lsmith.
Feb 19 11:07:24 uatappx2 systemd[1]: Started Session 227 of user lsmith.
Feb 19 11:07:24 uatappx2 systemd[39684]: Reached target Paths.
Feb 19 11:07:24 uatappx2 systemd[39684]: Reached target Sockets.
Feb 19 11:07:24 uatappx2 systemd[39684]: Reached target Timers.
Feb 19 11:07:24 uatappx2 systemd[39684]: Reached target Basic System.
Feb 19 11:07:24 uatappx2 systemd[39684]: Reached target Default.
Feb 19 11:07:24 uatappx2 systemd[39684]: Startup finished in 27ms.
Feb 19 11:07:24 uatappx2 systemd[1]: Started User Manager for UID 2017.
Feb 19 11:07:24 uatappx2 sshd[39680]: User child is on pid 39688
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: SELinux support disabled
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: PAM: establishing credentials
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: permanently_set_uid: 2017/100
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: rekey after 4294967296 blocks
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: rekey after 4294967296 blocks
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: ssh_packet_set_postauth: called
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: Entering interactive session for SSH2.
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: server_init_dispatch_20
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: input_session_request
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: channel 0: new [server-session]
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: session_new: session 0
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: session_open: channel 0
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: session_open: session 0: link with channel 0
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: server_input_channel_open: confirm session
Feb 19 11:07:24 uatappx2 sshd[39688]: Connection closed by 192.168.33.18
Feb 19 11:07:24 uatappx2 sshd[39688]: debug1: channel 0: free: server-session, nchannels 1

These connections worked on this server before doing an in-place upgrade to the new version, so the issue is definitely with the config of the sshd server vs what dejawin/putty is negotiating.

I have several other terminal software packages that do connect correctly.

Any thoughts?


 25 
 on: January 14, 2019, 11:43:08 am 
Started by jtshows - Last post by jtshows
I have a few installations where print screen (both the icon and by selecting file/print screen) does nothing.  Nothing prints, but the is correctly set up and prints for all other apps.  This seems to only affect a few machines, and seems to just suddenly start. 

anyone got any ideas?

 26 
 on: October 17, 2018, 08:58:01 am 
Started by JMartin - Last post by deanna
Have you removed/uninstalled the trialware version; you should only get that message if there is a trialware version installed.  Just to be clear, the trialware version does not convert to a permanent version anymore.  You have to install the permanent version.

 27 
 on: October 16, 2018, 03:21:23 am 
Started by JMartin - Last post by JMartin
Ice Tcp Pro on one PC every few weeks tells me that the trial license has expired, the other 4 PCs are fine.  I replaced all 5 PCs at one point so assume this has something to do with that.  I have run config wizard again but this has not resolved it, I uninstalled it and re-installed but a few weeks later get the same message.  Presumably there are some registry entries i need to clear out before re-installing again ?   Ice V 5.1  Windows 10.

 28 
 on: May 03, 2018, 10:51:44 am 
Started by dbonine - Last post by dbonine
We have recently applied a security update to AIX to use OpenSSH 7.5. The update is causing all ssh connections from ICETCP Pro DejaWinT to be disallowed. I have made the suggested change  to the sshd_config, but that does not work. We are using ICETCP 4.4.30. TCP PRO 5 doesn't work either. I have tried the newest version of TCP PRO 5.1.30 and ICETCP Plus build 30 without success. I get the ssh login box, type in the credentials and the window disappears with no connection.

I am able to make SSH connections with PuTTY and other emulator evaluation software.

 29 
 on: March 12, 2018, 12:15:16 pm 
Started by Hooper Info Tech - Last post by Bob
You could try the same method outlined here:

https://yabb.jriver.com/ice/index.php/topic,53391.msg56351.html#msg56351

 30 
 on: March 05, 2018, 03:37:33 pm 
Started by Hooper Info Tech - Last post by Hooper Info Tech
I'm attempting to install ICE Pro 5.1.25 onto a Microsoft surface tablet running Windows 10 version 1709 (Fall Creator's Update). I launch the installer, and the exe appears in the task manager, but then closes. There's no splash screen. No antivirus installed, and the firewall is disabled. I've successfully installed on previous versions of Win10, 1607 and 1703 without issue. This Surface came with 1709 loaded, so it's not possible to revert to an earlier version.

Is there a patch, or an alternative install method I can try?

Pages: 1 2 [3] 4 5 ... 10

Page created in 0.072 seconds with 17 queries.