Quantcast

Some struggle with SSH2DOS (solved)

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Some struggle with SSH2DOS (solved)

Ulrich Hansen-2
Hi all,

Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is great!

Unfortunately even this free SSH client is getting a bit rusty, the latest version is 11 years old.

As I found out, it wouldn’t connect to my server (Ubuntu 16.04 LTS).
But it still connected fine to a Debian Wheezy machine.

In the end I found the problem: OpenSSH versions >=6.7 have disabled a necessary KexAlgorithm and a Cipher.

Here is a report. I also posted it on the SSH2DOS page on SourceForge.

Hope this helps others eventually...
Ulrich



1. The solution:

Add the following lines to /etc/ssh/sshd_config on the server:

Ciphers aes128-cbc
KexAlgorithms diffie-hellman-group-exchange-sha1


2. The problem:

SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.

But it does not connect to a Debian 8 machine with OpenSSH 6.7.
It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.

SSH2DOS gives the following error code:

C:\> ssh2d386 username 192.168.1.136
SSH2DOS v0.2.1. 386+ version
Remote host closed connection
DH key exchange failed
Socket write error. File: transprt.c, line:698
Remote reset connection

On the server /var/log/auth.log says:
Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key exchange method [preauth]

SSH2D386 with the -d option writes the following DEBUG.PKT:


-------------------

RECEIVED packet:
14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26
E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D
73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72
67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74
70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E
69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61
32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69
65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D
65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C
64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67
72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73
73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D
35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36
2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74
70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63
2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32
35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F
70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D
36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75
6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E
63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35
36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C
68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61
63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74
6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D
61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E
63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E
73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61
63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D
73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68
61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E
6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68
2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00
00
.c.{i......i.2.&
.....curve25519-
[hidden email]
g,ecdh-sha2-nist
p256,ecdh-sha2-n
istp384,ecdh-sha
2-nistp521,diffi
e-hellman-group-
exchange-sha256,
diffie-hellman-g
roup14-sha1...As
sh-rsa,rsa-sha2-
512,rsa-sha2-256
,ecdsa-sha2-nist
p256,ssh-ed25519
...lchacha20-pol
[hidden email]
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-[hidden email]
...lchacha20-pol
[hidden email]
m,aes128-ctr,aes
192-ctr,aes256-c
tr,aes128-gcm@op
enssh.com,aes256
-[hidden email]
....umac-64-etm@
openssh.com,umac
-128-etm@openssh
.com,hmac-sha2-2
[hidden email]
om,hmac-sha2-512
-[hidden email]
,hmac-sha1-etm@o
penssh.com,umac-
[hidden email],u
mac-128@openssh.
com,hmac-sha2-25
6,hmac-sha2-512,
hmac-sha1....uma
c-64-etm@openssh
.com,umac-128-et
[hidden email],hm
ac-sha2-256-etm@
openssh.com,hmac
-sha2-512-etm@op
enssh.com,hmac-s
ha1-etm@openssh.
com,umac-64@open
ssh.com,umac-128
@openssh.com,hma
c-sha2-256,hmac-
sha2-512,hmac-sh
a1....none,zlib@
openssh.com....n
one,zlib@openssh
.com............
.

SENT packet:
14 8D 73 ED D0 96 BE 48 9A 89 61 74 E7 41 14 CE
FC 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
..s....H..at.A..
...."diffie-hell
man-group-exchan
ge-sha1....ssh-d
ss....aes128-cbc
....aes128-cbc..
..hmac-sha1....h
mac-sha1....none
,zlib....none,zl
ib.............

SENT packet:
1E 00 00 04 00
.....

SENT packet:
62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
00 18 00 00 00 00 00 00 00 00 00 00 00 00
b........pty-req
.....xterm...P..
..............
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Ulrich Hansen-2
Update:

The solution I found last night seems to work only for older OpenSSH servers.

For Ubuntu 16.04 LTS (with OpenSSH 7.2.) I also had to add:

HostKeyAlgorithms ssh-dss

to /etc/ssh/sshd_config because ssh-dss seems to have been deactivated by default since OpenSSH 6.9.

But in the end SSH2DOS was still not able to connect to OpenSSH 7.2.

Perhaps someone has an idea?

At the moment SSH2DOS can only be used to connect to older servers, running f.i. Debian Wheezy (OpenSSH 6.0) or Jessie (OpenSSH 6.7).

So soon there will be no functioning SSH client anymore for FreeDOS. :-(

Here are the messages:

SSH2DOS error message is:

C:\> ssh2d386 username 192.168.1.131
SSH2DOS v0.2.1. 386+ version
Expected KEX_DH_GEX_GROUP
DH key exchange failed
Remote host closed connection
Socket write error. File: transprt.c, line:698
Connection closed by peer

On the server, Ubuntu 16.04 LTS (with OpenSSH 7.2.), /var/log/auth.log says:

Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: kex protocol error: type 30 seq 1 [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: Received disconnect from 192.168.1.110 port 564:3: Expected KEX_DH_GEX_GROUP [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: Disconnected from 192.168.1.110 port 564 [preauth]


C:\> ssh2d386 -d username 192.168.1.131

wrote the following output in C:\SSH2DOS\DEBUG.PKT:

-------------------

RECEIVED packet:
14 BE 6D 01 48 D3 E5 EB 2A C1 81 DE E7 31 AB DB
B2 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31
32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2D 65
74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68
6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 70 65
6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 36 34
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61
63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2C
68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 68 6D
61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 63 2D
36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 65 6E
73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61
31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 73 73
68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 40 6F
70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D
73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 73 68
61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 61 31
00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 6F 6E
65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 00 00 00 00 00 00 00 00 00 00 00 00 00
..m.H...*....1..
...."diffie-hell
man-group-exchan
ge-sha1....ssh-d
ss....aes128-cbc
....aes128-cbc..
..umac-64-etm@op
enssh.com,umac-1
[hidden email]
om,hmac-sha2-256
-[hidden email]
,hmac-sha2-512-e
[hidden email],h
mac-sha1-etm@ope
nssh.com,umac-64
@openssh.com,uma
[hidden email]
m,hmac-sha2-256,
hmac-sha2-512,hm
ac-sha1....umac-
[hidden email]
om,umac-128-etm@
openssh.com,hmac
-sha2-256-etm@op
enssh.com,hmac-s
ha2-512-etm@open
ssh.com,hmac-sha
[hidden email]
m,umac-64@openss
h.com,umac-128@o
penssh.com,hmac-
sha2-256,hmac-sh
a2-512,hmac-sha1
....none,zlib@op
enssh.com....non
e,[hidden email]
om.............

SENT packet:
14 25 81 88 A7 CD 90 15 0E 5E 3B 7C B4 0B 1E 9D
CA 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
.%.......^;|....
...."diffie-hell
man-group-exchan
ge-sha1....ssh-d
ss....aes128-cbc
....aes128-cbc..
..hmac-sha1....h
mac-sha1....none
,zlib....none,zl
ib.............

SENT packet:
1E 00 00 04 00
.....

RECEIVED packet:
03 00 00 00 01
.....

SENT packet:
03 00 00 00 02
.....

SENT packet:
01 00 00 00 03 00 00 00 19 45 78 70 65 63 74 65
64 20 4B 45 58 5F 44 48 5F 47 45 58 5F 47 52 4F
55 50 00 00 00 00
.........Expecte
d KEX_DH_GEX_GRO
UP....

SENT packet:
62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
00 18 00 00 00 00 00 00 00 00 00 00 00 00
b........pty-req
.....xterm...P..
..............

SENT packet:
62 00 00 00 00 00 00 00 05 73 68 65 6C 6C 01
b........shell.






> Am 23.01.2017 um 01:22 schrieb Ulrich Hansen <[hidden email]>:
>
> Hi all,
>
> Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is great!
>
> Unfortunately even this free SSH client is getting a bit rusty, the latest version is 11 years old.
>
> As I found out, it wouldn’t connect to my server (Ubuntu 16.04 LTS).
> But it still connected fine to a Debian Wheezy machine.
>
> In the end I found the problem: OpenSSH versions >=6.7 have disabled a necessary KexAlgorithm and a Cipher.
>
> Here is a report. I also posted it on the SSH2DOS page on SourceForge.
>
> Hope this helps others eventually...
> Ulrich
>
>
>
> 1. The solution:
>
> Add the following lines to /etc/ssh/sshd_config on the server:
>
> Ciphers aes128-cbc
> KexAlgorithms diffie-hellman-group-exchange-sha1
>
>
> 2. The problem:
>
> SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.
>
> But it does not connect to a Debian 8 machine with OpenSSH 6.7.
> It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.
>
> SSH2DOS gives the following error code:
>
> C:\> ssh2d386 username 192.168.1.136
> SSH2DOS v0.2.1. 386+ version
> Remote host closed connection
> DH key exchange failed
> Socket write error. File: transprt.c, line:698
> Remote reset connection
>
> On the server /var/log/auth.log says:
> Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key exchange method [preauth]
>
> SSH2D386 with the -d option writes the following DEBUG.PKT:
>
>
> -------------------
>
> RECEIVED packet:
> 14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26
> E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D
> 73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72
> 67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74
> 70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E
> 69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61
> 32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69
> 65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D
> 65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C
> 64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67
> 72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73
> 73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D
> 35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36
> 2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74
> 70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63
> 2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32
> 35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
> 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32
> 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F
> 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D
> 36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75
> 6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E
> 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35
> 36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C
> 68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61
> 63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74
> 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D
> 61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
> 2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
> 68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E
> 63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E
> 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38
> 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61
> 63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D
> 73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68
> 61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E
> 6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> .c.{i......i.2.&
> .....curve25519-
> [hidden email]
> g,ecdh-sha2-nist
> p256,ecdh-sha2-n
> istp384,ecdh-sha
> 2-nistp521,diffi
> e-hellman-group-
> exchange-sha256,
> diffie-hellman-g
> roup14-sha1...As
> sh-rsa,rsa-sha2-
> 512,rsa-sha2-256
> ,ecdsa-sha2-nist
> p256,ssh-ed25519
> ...lchacha20-pol
> [hidden email]
> m,aes128-ctr,aes
> 192-ctr,aes256-c
> tr,aes128-gcm@op
> enssh.com,aes256
> -[hidden email]
> ...lchacha20-pol
> [hidden email]
> m,aes128-ctr,aes
> 192-ctr,aes256-c
> tr,aes128-gcm@op
> enssh.com,aes256
> -[hidden email]
> ....umac-64-etm@
> openssh.com,umac
> -128-etm@openssh
> .com,hmac-sha2-2
> [hidden email]
> om,hmac-sha2-512
> -[hidden email]
> ,hmac-sha1-etm@o
> penssh.com,umac-
> [hidden email],u
> mac-128@openssh.
> com,hmac-sha2-25
> 6,hmac-sha2-512,
> hmac-sha1....uma
> c-64-etm@openssh
> .com,umac-128-et
> [hidden email],hm
> ac-sha2-256-etm@
> openssh.com,hmac
> -sha2-512-etm@op
> enssh.com,hmac-s
> ha1-etm@openssh.
> com,umac-64@open
> ssh.com,umac-128
> @openssh.com,hma
> c-sha2-256,hmac-
> sha2-512,hmac-sh
> a1....none,zlib@
> openssh.com....n
> one,zlib@openssh
> .com............
> .
>
> SENT packet:
> 14 8D 73 ED D0 96 BE 48 9A 89 61 74 E7 41 14 CE
> FC 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
> 6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
> 67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
> 73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
> 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
> 00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
> 6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
> 2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
> 69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
> ..s....H..at.A..
> ...."diffie-hell
> man-group-exchan
> ge-sha1....ssh-d
> ss....aes128-cbc
> ....aes128-cbc..
> ..hmac-sha1....h
> mac-sha1....none
> ,zlib....none,zl
> ib.............
>
> SENT packet:
> 1E 00 00 04 00
> .....
>
> SENT packet:
> 62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
> 01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
> 00 18 00 00 00 00 00 00 00 00 00 00 00 00
> b........pty-req
> .....xterm...P..
> ..............
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Freedos-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
They deprecated that cipher - you can make it work, but it is vulnerable.  Also, ssh2dos is very unstable in my experience.  I wish somebody would write a decent ssh for dos.  

On Mon, Jan 23, 2017 at 1:21 AM, Ulrich Hansen <[hidden email]> wrote:
Update:

The solution I found last night seems to work only for older OpenSSH servers.

For Ubuntu 16.04 LTS (with OpenSSH 7.2.) I also had to add:

HostKeyAlgorithms ssh-dss

to /etc/ssh/sshd_config because ssh-dss seems to have been deactivated by default since OpenSSH 6.9.

But in the end SSH2DOS was still not able to connect to OpenSSH 7.2.

Perhaps someone has an idea?

At the moment SSH2DOS can only be used to connect to older servers, running f.i. Debian Wheezy (OpenSSH 6.0) or Jessie (OpenSSH 6.7).

So soon there will be no functioning SSH client anymore for FreeDOS. :-(

Here are the messages:

SSH2DOS error message is:

C:\> ssh2d386 username 192.168.1.131
SSH2DOS v0.2.1. 386+ version
Expected KEX_DH_GEX_GROUP
DH key exchange failed
Remote host closed connection
Socket write error. File: transprt.c, line:698
Connection closed by peer

On the server, Ubuntu 16.04 LTS (with OpenSSH 7.2.), /var/log/auth.log says:

Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: kex protocol error: type 30 seq 1 [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: error: Received disconnect from 192.168.1.110 port 564:3: Expected KEX_DH_GEX_GROUP [preauth]
Jan 23 09:55:09 ubuntu-VirtualBox sshd[4661]: Disconnected from 192.168.1.110 port 564 [preauth]


C:\> ssh2d386 -d username 192.168.1.131

wrote the following output in C:\SSH2DOS\DEBUG.PKT:

-------------------

RECEIVED packet:
14 BE 6D 01 48 D3 E5 EB 2A C1 81 DE E7 31 AB DB
B2 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31
32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36
2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2D 65
74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68
6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F 70 65
6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 36 34
40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61
63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35 36 2C
68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C 68 6D
61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61 63 2D
36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74 6D 40
6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70 65 6E
73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61
31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F
6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E 73 73
68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 40 6F
70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D
73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D 73 68
61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68 61 31
00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40 6F 70
65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E 6F 6E
65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68 2E 63
6F 6D 00 00 00 00 00 00 00 00 00 00 00 00 00
..m.H...*....1..
...."diffie-hell
man-group-exchan
ge-sha1....ssh-d
ss....aes128-cbc
....aes128-cbc..
..umac-64-etm@op
enssh.com,umac-1
[hidden email]
om,hmac-sha2-256
-[hidden email]
,hmac-sha2-512-e
[hidden email],h
mac-sha1-etm@ope
nssh.com,umac-64
@openssh.com,uma
[hidden email]
m,hmac-sha2-256,
hmac-sha2-512,hm
ac-sha1....umac-
[hidden email]
om,umac-128-etm@
openssh.com,hmac
-sha2-256-etm@op
enssh.com,hmac-s
ha2-512-etm@open
ssh.com,hmac-sha
[hidden email]
m,umac-64@openss
h.com,umac-128@o
penssh.com,hmac-
sha2-256,hmac-sh
a2-512,hmac-sha1
....none,zlib@op
enssh.com....non
e,[hidden email]
om.............

SENT packet:
14 25 81 88 A7 CD 90 15 0E 5E 3B 7C B4 0B 1E 9D
CA 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
.%.......^;|....
...."diffie-hell
man-group-exchan
ge-sha1....ssh-d
ss....aes128-cbc
....aes128-cbc..
..hmac-sha1....h
mac-sha1....none
,zlib....none,zl
ib.............

SENT packet:
1E 00 00 04 00
.....

RECEIVED packet:
03 00 00 00 01
.....

SENT packet:
03 00 00 00 02
.....

SENT packet:
01 00 00 00 03 00 00 00 19 45 78 70 65 63 74 65
64 20 4B 45 58 5F 44 48 5F 47 45 58 5F 47 52 4F
55 50 00 00 00 00
.........Expecte
d KEX_DH_GEX_GRO
UP....

SENT packet:
62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
00 18 00 00 00 00 00 00 00 00 00 00 00 00
b........pty-req
.....xterm...P..
..............

SENT packet:
62 00 00 00 00 00 00 00 05 73 68 65 6C 6C 01
b........shell.






> Am 23.01.2017 um 01:22 schrieb Ulrich Hansen <[hidden email]>:
>
> Hi all,
>
> Thanks to Jerome, there is now SSH2DOS in the FreeDOS net repo, which is great!
>
> Unfortunately even this free SSH client is getting a bit rusty, the latest version is 11 years old.
>
> As I found out, it wouldn’t connect to my server (Ubuntu 16.04 LTS).
> But it still connected fine to a Debian Wheezy machine.
>
> In the end I found the problem: OpenSSH versions >=6.7 have disabled a necessary KexAlgorithm and a Cipher.
>
> Here is a report. I also posted it on the SSH2DOS page on SourceForge.
>
> Hope this helps others eventually...
> Ulrich
>
>
>
> 1. The solution:
>
> Add the following lines to /etc/ssh/sshd_config on the server:
>
> Ciphers aes128-cbc
> KexAlgorithms diffie-hellman-group-exchange-sha1
>
>
> 2. The problem:
>
> SSH2DOS works fine with a Debian Wheezy machine with OpenSSH 6.0.
>
> But it does not connect to a Debian 8 machine with OpenSSH 6.7.
> It also does not connect to a Ubuntu 16.04 server with OpenSSH 7.2.
>
> SSH2DOS gives the following error code:
>
> C:\> ssh2d386 username 192.168.1.136
> SSH2DOS v0.2.1. 386+ version
> Remote host closed connection
> DH key exchange failed
> Socket write error. File: transprt.c, line:698
> Remote reset connection
>
> On the server /var/log/auth.log says:
> Jan 23 00:17:25 debian8 sshd [1883]: fatal: Unable to negotiate a key exchange method [preauth]
>
> SSH2D386 with the -d option writes the following DEBUG.PKT:
>
>
> -------------------
>
> RECEIVED packet:
> 14 63 99 7B 69 DA 8E 90 00 02 0A 69 D1 32 93 26
> E1 00 00 00 96 63 75 72 76 65 32 35 35 31 39 2D
> 73 68 61 32 35 36 40 6C 69 62 73 73 68 2E 6F 72
> 67 2C 65 63 64 68 2D 73 68 61 32 2D 6E 69 73 74
> 70 32 35 36 2C 65 63 64 68 2D 73 68 61 32 2D 6E
> 69 73 74 70 33 38 34 2C 65 63 64 68 2D 73 68 61
> 32 2D 6E 69 73 74 70 35 32 31 2C 64 69 66 66 69
> 65 2D 68 65 6C 6C 6D 61 6E 2D 67 72 6F 75 70 2D
> 65 78 63 68 61 6E 67 65 2D 73 68 61 32 35 36 2C
> 64 69 66 66 69 65 2D 68 65 6C 6C 6D 61 6E 2D 67
> 72 6F 75 70 31 34 2D 73 68 61 31 00 00 00 41 73
> 73 68 2D 72 73 61 2C 72 73 61 2D 73 68 61 32 2D
> 35 31 32 2C 72 73 61 2D 73 68 61 32 2D 32 35 36
> 2C 65 63 64 73 61 2D 73 68 61 32 2D 6E 69 73 74
> 70 32 35 36 2C 73 73 68 2D 65 64 32 35 35 31 39
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 00 00 00 6C 63 68 61 63 68 61 32 30 2D 70 6F 6C
> 79 31 33 30 35 40 6F 70 65 6E 73 73 68 2E 63 6F
> 6D 2C 61 65 73 31 32 38 2D 63 74 72 2C 61 65 73
> 31 39 32 2D 63 74 72 2C 61 65 73 32 35 36 2D 63
> 74 72 2C 61 65 73 31 32 38 2D 67 63 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 61 65 73 32 35 36
> 2D 67 63 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 00 00 00 D5 75 6D 61 63 2D 36 34 2D 65 74 6D 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63
> 2D 31 32 38 2D 65 74 6D 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32
> 35 36 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63
> 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32
> 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D
> 2C 68 6D 61 63 2D 73 68 61 31 2D 65 74 6D 40 6F
> 70 65 6E 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D
> 36 34 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 75
> 6D 61 63 2D 31 32 38 40 6F 70 65 6E 73 73 68 2E
> 63 6F 6D 2C 68 6D 61 63 2D 73 68 61 32 2D 32 35
> 36 2C 68 6D 61 63 2D 73 68 61 32 2D 35 31 32 2C
> 68 6D 61 63 2D 73 68 61 31 00 00 00 D5 75 6D 61
> 63 2D 36 34 2D 65 74 6D 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38 2D 65 74
> 6D 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D
> 61 63 2D 73 68 61 32 2D 32 35 36 2D 65 74 6D 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63
> 2D 73 68 61 32 2D 35 31 32 2D 65 74 6D 40 6F 70
> 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61 63 2D 73
> 68 61 31 2D 65 74 6D 40 6F 70 65 6E 73 73 68 2E
> 63 6F 6D 2C 75 6D 61 63 2D 36 34 40 6F 70 65 6E
> 73 73 68 2E 63 6F 6D 2C 75 6D 61 63 2D 31 32 38
> 40 6F 70 65 6E 73 73 68 2E 63 6F 6D 2C 68 6D 61
> 63 2D 73 68 61 32 2D 32 35 36 2C 68 6D 61 63 2D
> 73 68 61 32 2D 35 31 32 2C 68 6D 61 63 2D 73 68
> 61 31 00 00 00 15 6E 6F 6E 65 2C 7A 6C 69 62 40
> 6F 70 65 6E 73 73 68 2E 63 6F 6D 00 00 00 15 6E
> 6F 6E 65 2C 7A 6C 69 62 40 6F 70 65 6E 73 73 68
> 2E 63 6F 6D 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> .c.{i......i.2.&
> .....curve25519-
> [hidden email]
> g,ecdh-sha2-nist
> p256,ecdh-sha2-n
> istp384,ecdh-sha
> 2-nistp521,diffi
> e-hellman-group-
> exchange-sha256,
> diffie-hellman-g
> roup14-sha1...As
> sh-rsa,rsa-sha2-
> 512,rsa-sha2-256
> ,ecdsa-sha2-nist
> p256,ssh-ed25519
> ...lchacha20-pol
> [hidden email]
> m,aes128-ctr,aes
> 192-ctr,aes256-c
> tr,aes128-gcm@op
> enssh.com,aes256
> -[hidden email]
> ...lchacha20-pol
> [hidden email]
> m,aes128-ctr,aes
> 192-ctr,aes256-c
> tr,aes128-gcm@op
> enssh.com,aes256
> -[hidden email]
> ....umac-64-etm@
> openssh.com,umac
> -128-etm@openssh
> .com,hmac-sha2-2
> [hidden email]
> om,hmac-sha2-512
> -[hidden email]
> ,hmac-sha1-etm@o
> penssh.com,umac-
> [hidden email],u
> mac-128@openssh.
> com,hmac-sha2-25
> 6,hmac-sha2-512,
> hmac-sha1....uma
> c-64-etm@openssh
> .com,umac-128-et
> [hidden email],hm
> ac-sha2-256-etm@
> openssh.com,hmac
> -sha2-512-etm@op
> enssh.com,hmac-s
> ha1-etm@openssh.
> com,umac-64@open
> ssh.com,umac-128
> @openssh.com,hma
> c-sha2-256,hmac-
> sha2-512,hmac-sh
> a1....none,zlib@
> openssh.com....n
> one,zlib@openssh
> .com............
> .
>
> SENT packet:
> 14 8D 73 ED D0 96 BE 48 9A 89 61 74 E7 41 14 CE
> FC 00 00 00 22 64 69 66 66 69 65 2D 68 65 6C 6C
> 6D 61 6E 2D 67 72 6F 75 70 2D 65 78 63 68 61 6E
> 67 65 2D 73 68 61 31 00 00 00 07 73 73 68 2D 64
> 73 73 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63
> 00 00 00 0A 61 65 73 31 32 38 2D 63 62 63 00 00
> 00 09 68 6D 61 63 2D 73 68 61 31 00 00 00 09 68
> 6D 61 63 2D 73 68 61 31 00 00 00 09 6E 6F 6E 65
> 2C 7A 6C 69 62 00 00 00 09 6E 6F 6E 65 2C 7A 6C
> 69 62 00 00 00 00 00 00 00 00 00 00 00 00 00
> ..s....H..at.A..
> ...."diffie-hell
> man-group-exchan
> ge-sha1....ssh-d
> ss....aes128-cbc
> ....aes128-cbc..
> ..hmac-sha1....h
> mac-sha1....none
> ,zlib....none,zl
> ib.............
>
> SENT packet:
> 1E 00 00 04 00
> .....
>
> SENT packet:
> 62 00 00 00 00 00 00 00 07 70 74 79 2D 72 65 71
> 01 00 00 00 05 78 74 65 72 6D 00 00 00 50 00 00
> 00 18 00 00 00 00 00 00 00 00 00 00 00 00
> b........pty-req
> .....xterm...P..
> ..............
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Freedos-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Bret
In reply to this post by Ulrich Hansen-2
> I wish somebody would write a decent ssh for dos.

Could that somebody be you?
____________________________________________________________
Another Scandal Hits TLC...Will The Network Survive This One
trend-chaser.com
http://thirdpartyoffers.juno.com/TGL3141/588a191272bac19125e24st01vuc

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Karen Lewellen
Hi,
I am sorry if I missed this thread.
As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.
for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.
may I ask again what your issue is presently?
Karen


On Thu, 26 Jan 2017, Bret Johnson wrote:

>> I wish somebody would write a decent ssh for dos.
>
> Could that somebody be you?
> ____________________________________________________________
> Another Scandal Hits TLC...Will The Network Survive This One
> trend-chaser.com
> http://thirdpartyoffers.juno.com/TGL3141/588a191272bac19125e24st01vuc
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Freedos-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Ulrich Hansen-2

> Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:
>
> As I am presently writing this e-mail using ssh2d386 from the ssh2dos
> package ssh2021b,  perhaps I can help you troubleshoot.

Hi Karen!

I am using the exact same program and version.

> for the record, I am not using freedos, but  the ms dos 7.10 package
> mentioned on this list.
> Still every day several times a day I connect  to two different servers
> using  this package.

I guess your servers still run OpenSSH in versions earlier than 6.9.

> may I ask again what your issue is presently?

Actually I have given up on it. I spent another day trying to get it to work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with OpenSSH 7.2.

SSH2D386 gives the message:

     Expected KEX_DH_GEX_GROUP
     DH key exchange failed

The server logs:
     Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol error: type 30 seq 1 [preauth]
     Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the server.

     Ciphers aes128-cbc
     KexAlgorithms diffie-hellman-group-exchange-sha1
     MACs hmac-sha1
     HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
     { "SSHDOS*", SSH_OLD_DHGEX },
The second time with this one:
     { "SSHDOS*", SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already several exceptions in combat.c for old PuTTY versions. The reason seems to be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with OpenWatcom. I installed it but gave up, when I saw I also had to compile the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rfc4419.html



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Karen Lewellen
Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office,
and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g
option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with
allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare


On Fri, 27 Jan 2017, Ulrich Hansen wrote:

>
>> Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:
>>
>> As I am presently writing this e-mail using ssh2d386 from the ssh2dos
>> package ssh2021b,  perhaps I can help you troubleshoot.
>
> Hi Karen!
>
> I am using the exact same program and version.
>
>> for the record, I am not using freedos, but  the ms dos 7.10 package
>> mentioned on this list.
>> Still every day several times a day I connect  to two different servers
>> using  this package.
>
> I guess your servers still run OpenSSH in versions earlier than 6.9.
>
>> may I ask again what your issue is presently?
>
> Actually I have given up on it. I spent another day trying to get it to work, but without success.
>
> The problem is that I can’t connect to an Ubuntu 16.04 LTS server with OpenSSH 7.2.
>
> SSH2D386 gives the message:
>
>     Expected KEX_DH_GEX_GROUP
>     DH key exchange failed
>
> The server logs:
>     Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol error: type 30 seq 1 [preauth]
>     Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO
>
> As I wrote I already had problems connecting to a Debian 8 server with OpenSSH 6.7.
> But there I could fix it with these lines in /etc/ssh/sshd_config on the server.
>
>     Ciphers aes128-cbc
>     KexAlgorithms diffie-hellman-group-exchange-sha1
>     MACs hmac-sha1
>     HostKeyAlgorithms ssh-css
>
> But in OpenSSH 7.2 this didn’t work.
>
> What else did I try?
>
> I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.
>
> I tried to recompile OpenSSH.
> The first time with adding this line in in compat.c:
>     { "SSHDOS*", SSH_OLD_DHGEX },
> The second time with this one:
>     { "SSHDOS*", SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },
>
> Both were not able to let SSH2D386 connect. It worked great with other SSH clients.
>
> The idea was that SSH2DOS uses code from PuTTY and there were already several exceptions in combat.c for old PuTTY versions. The reason seems to be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did not. See [1], [2].
>
> I even looked at the SSH2DOS source code. But I have no experience with OpenWatcom. I installed it but gave up, when I saw I also had to compile the WATT32 TCP/IP stack.
>
> SSH2DOS uses PuTTY code, which is also Free Software. So in theory it should be possible to replace the old PuTTY code with a more recent one.
>
> cheers
> Ulrich
>
>
> [1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
> [2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rfc4419.html
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Freedos-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

William Dudley
Karen,

If you know how to get ssh2d386 to connect to a modern openssh, as on Ubuntu 16.04,
please share the recipe with us!

Thanks,
Bill Dudley


This email is free of malware because I run Linux.

On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen <[hidden email]> wrote:
Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office, and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare



On Fri, 27 Jan 2017, Ulrich Hansen wrote:


Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:

As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.

Hi Karen!

I am using the exact same program and version.

for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.

I guess your servers still run OpenSSH in versions earlier than 6.9.

may I ask again what your issue is presently?

Actually I have given up on it. I spent another day trying to get it to work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with OpenSSH 7.2.

SSH2D386 gives the message:

    Expected KEX_DH_GEX_GROUP
    DH key exchange failed

The server logs:
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol error: type 30 seq 1 [preauth]
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the server.

    Ciphers aes128-cbc
    KexAlgorithms diffie-hellman-group-exchange-sha1
    MACs hmac-sha1
    HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
    { "SSHDOS*",                SSH_OLD_DHGEX },
The second time with this one:
    { "SSHDOS*",                SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already several exceptions in combat.c for old PuTTY versions. The reason seems to be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with OpenWatcom. I installed it but gave up, when I saw I also had to compile the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rfc4419.html



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Karen Lewellen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue? 

I would like to answer Ulrich on how he can modify his Ubuntu server, but first, a warning: These algorithms were disabled because they are obsolete and insecure.  Using a token based login, such as google-authenticator, may be advisable if your server is public facing.  

Firstly, add this to your server's /etc/ssh/sshd_config:

KexAlgorithms diffie-hellman-group1-sha1,[hidden email],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
HostKeyAlgorithms +ssh-dss

Then, make use of the -g option - it goes BEFORE your username in ssh2dos.  You should now be able to connect.  

I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it seems it should.  Also, I was in a rush - I may be excluding some newer options - report back if you find/add them with success. 

-Dan

On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <[hidden email]> wrote:
Hi Bill,
While I appreciate your desire for wisdom, I feel rather sure  my specific situation will not apply to anyone else here most likely.
I use ssh2d386 to  access at least one commercial shell, but those shell services are maintained by others.  I am not for example accessing my own server.
If the servers you desire reaching are run by other people,  give me an example and I will try.
If my many years of computing has taught me anything is that the word Personal  is important for a reason.
Kare



On Thu, 26 Jan 2017, William Dudley wrote:

Karen,

If you know how to get ssh2d386 to connect to a modern openssh, as on
Ubuntu 16.04,
please share the recipe with us!

Thanks,
Bill Dudley


This email is free of malware because I run Linux.

On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen <[hidden email]>
wrote:

Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office,
and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g
option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with
allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare



On Fri, 27 Jan 2017, Ulrich Hansen wrote:


Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:

As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.


Hi Karen!

I am using the exact same program and version.

for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.


I guess your servers still run OpenSSH in versions earlier than 6.9.

may I ask again what your issue is presently?


Actually I have given up on it. I spent another day trying to get it to
work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with
OpenSSH 7.2.

SSH2D386 gives the message:

    Expected KEX_DH_GEX_GROUP
    DH key exchange failed

The server logs:
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
error: type 30 seq 1 [preauth]
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with
OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the
server.

    Ciphers aes128-cbc
    KexAlgorithms diffie-hellman-group-exchange-sha1
    MACs hmac-sha1
    HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
    { "SSHDOS*",                SSH_OLD_DHGEX },
The second time with this one:
    { "SSHDOS*",                SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other
SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already
several exceptions in combat.c for old PuTTY versions. The reason seems to
be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did
not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with
OpenWatcom. I installed it but gave up, when I saw I also had to compile
the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it
should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/
rfc4419.html



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
I forgot - you may need to regenerate your keys with "ssh-keygen -A" after modifying the server. 

On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt <[hidden email]> wrote:
I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue? 

I would like to answer Ulrich on how he can modify his Ubuntu server, but first, a warning: These algorithms were disabled because they are obsolete and insecure.  Using a token based login, such as google-authenticator, may be advisable if your server is public facing.  

Firstly, add this to your server's /etc/ssh/sshd_config:

KexAlgorithms diffie-hellman-group1-sha1,[hidden email],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
HostKeyAlgorithms +ssh-dss

Then, make use of the -g option - it goes BEFORE your username in ssh2dos.  You should now be able to connect.  

I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it seems it should.  Also, I was in a rush - I may be excluding some newer options - report back if you find/add them with success. 

-Dan

On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <[hidden email]> wrote:
Hi Bill,
While I appreciate your desire for wisdom, I feel rather sure  my specific situation will not apply to anyone else here most likely.
I use ssh2d386 to  access at least one commercial shell, but those shell services are maintained by others.  I am not for example accessing my own server.
If the servers you desire reaching are run by other people,  give me an example and I will try.
If my many years of computing has taught me anything is that the word Personal  is important for a reason.
Kare



On Thu, 26 Jan 2017, William Dudley wrote:

Karen,

If you know how to get ssh2d386 to connect to a modern openssh, as on
Ubuntu 16.04,
please share the recipe with us!

Thanks,
Bill Dudley


This email is free of malware because I run Linux.

On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen <[hidden email]>
wrote:

Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office,
and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g
option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with
allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare



On Fri, 27 Jan 2017, Ulrich Hansen wrote:


Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:

As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.


Hi Karen!

I am using the exact same program and version.

for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.


I guess your servers still run OpenSSH in versions earlier than 6.9.

may I ask again what your issue is presently?


Actually I have given up on it. I spent another day trying to get it to
work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with
OpenSSH 7.2.

SSH2D386 gives the message:

    Expected KEX_DH_GEX_GROUP
    DH key exchange failed

The server logs:
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
error: type 30 seq 1 [preauth]
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with
OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the
server.

    Ciphers aes128-cbc
    KexAlgorithms diffie-hellman-group-exchange-sha1
    MACs hmac-sha1
    HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
    { "SSHDOS*",                SSH_OLD_DHGEX },
The second time with this one:
    { "SSHDOS*",                SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other
SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already
several exceptions in combat.c for old PuTTY versions. The reason seems to
be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did
not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with
OpenWatcom. I installed it but gave up, when I saw I also had to compile
the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it
should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/
rfc4419.html



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Ulrich Hansen-2
Wow. I am stunned. This has solved the problem. I have spent more than a day searching for such a solution.

I am now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2
Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos with "FDNPKG install ssh2dos"

Thank you very, very much!

Ulrich



Am 27.01.2017 um 06:39 schrieb Dan Schmidt <[hidden email]>:

I forgot - you may need to regenerate your keys with "ssh-keygen -A" after modifying the server. 

On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt <[hidden email]> wrote:
I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue? 

I would like to answer Ulrich on how he can modify his Ubuntu server, but first, a warning: These algorithms were disabled because they are obsolete and insecure.  Using a token based login, such as google-authenticator, may be advisable if your server is public facing.  

Firstly, add this to your server's /etc/ssh/sshd_config:

KexAlgorithms diffie-hellman-group1-sha1,[hidden email],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
HostKeyAlgorithms +ssh-dss

Then, make use of the -g option - it goes BEFORE your username in ssh2dos.  You should now be able to connect.  

I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it seems it should.  Also, I was in a rush - I may be excluding some newer options - report back if you find/add them with success. 

-Dan

On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <[hidden email]> wrote:
Hi Bill,
While I appreciate your desire for wisdom, I feel rather sure  my specific situation will not apply to anyone else here most likely.
I use ssh2d386 to  access at least one commercial shell, but those shell services are maintained by others.  I am not for example accessing my own server.
If the servers you desire reaching are run by other people,  give me an example and I will try.
If my many years of computing has taught me anything is that the word Personal  is important for a reason.
Kare



On Thu, 26 Jan 2017, William Dudley wrote:

Karen,

If you know how to get ssh2d386 to connect to a modern openssh, as on
Ubuntu 16.04,
please share the recipe with us!

Thanks,
Bill Dudley


This email is free of malware because I run Linux.

On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen <[hidden email]>
wrote:

Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office,
and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g
option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with
allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare



On Fri, 27 Jan 2017, Ulrich Hansen wrote:


Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:

As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.


Hi Karen!

I am using the exact same program and version.

for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.


I guess your servers still run OpenSSH in versions earlier than 6.9.

may I ask again what your issue is presently?


Actually I have given up on it. I spent another day trying to get it to
work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with
OpenSSH 7.2.

SSH2D386 gives the message:

    Expected KEX_DH_GEX_GROUP
    DH key exchange failed

The server logs:
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
error: type 30 seq 1 [preauth]
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with
OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the
server.

    Ciphers aes128-cbc
    KexAlgorithms diffie-hellman-group-exchange-sha1
    MACs hmac-sha1
    HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
    { "SSHDOS*",                SSH_OLD_DHGEX },
The second time with this one:
    { "SSHDOS*",                SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other
SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already
several exceptions in combat.c for old PuTTY versions. The reason seems to
be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did
not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with
OpenWatcom. I installed it but gave up, when I saw I also had to compile
the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it
should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/
rfc4419.html



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
I am equally as stunned - I will remember this day as the day I tried to help somebody on the internet and they said "thank you" instead of flaming or ignoring me. 

My ssh2dos is very unstable - it usually crashes on exit or after five to ten minutes.  Do you have this issue as well?  I am curious if I should try a different version of DOS.  

On Fri, Jan 27, 2017 at 12:04 AM, Ulrich Hansen <[hidden email]> wrote:
Wow. I am stunned. This has solved the problem. I have spent more than a day searching for such a solution.

I am now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2
Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos with "FDNPKG install ssh2dos"

Thank you very, very much!

Ulrich



Am 27.01.2017 um 06:39 schrieb Dan Schmidt <[hidden email]>:

I forgot - you may need to regenerate your keys with "ssh-keygen -A" after modifying the server. 

On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt <[hidden email]> wrote:
I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue? 

I would like to answer Ulrich on how he can modify his Ubuntu server, but first, a warning: These algorithms were disabled because they are obsolete and insecure.  Using a token based login, such as google-authenticator, may be advisable if your server is public facing.  

Firstly, add this to your server's /etc/ssh/sshd_config:

KexAlgorithms diffie-hellman-group1-sha1,[hidden email],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
Ciphers 3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr
HostKeyAlgorithms +ssh-dss

Then, make use of the -g option - it goes BEFORE your username in ssh2dos.  You should now be able to connect.  

I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it seems it should.  Also, I was in a rush - I may be excluding some newer options - report back if you find/add them with success. 

-Dan

On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <[hidden email]> wrote:
Hi Bill,
While I appreciate your desire for wisdom, I feel rather sure  my specific situation will not apply to anyone else here most likely.
I use ssh2d386 to  access at least one commercial shell, but those shell services are maintained by others.  I am not for example accessing my own server.
If the servers you desire reaching are run by other people,  give me an example and I will try.
If my many years of computing has taught me anything is that the word Personal  is important for a reason.
Kare



On Thu, 26 Jan 2017, William Dudley wrote:

Karen,

If you know how to get ssh2d386 to connect to a modern openssh, as on
Ubuntu 16.04,
please share the recipe with us!

Thanks,
Bill Dudley


This email is free of malware because I run Linux.

On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen <[hidden email]>
wrote:

Well, if you have given up no point in my sharing.
We use the same edition of Ubuntu, both with dreamhost who has my office,
and here at shellworld.
While the latter requires me to make use of a few ssh2021b options, the -g
option  for example, I encounter no issues.
I am going to guess that  things like machine speed, mine is a p3 with
allot of memory, impacts your situation.
nor, I would hope, your  location in the world.
Sorry I did not notice your post before you abandoned  the effort.
Kare



On Fri, 27 Jan 2017, Ulrich Hansen wrote:


Am 26.01.2017 um 18:19 schrieb Karen Lewellen <[hidden email]>:

As I am presently writing this e-mail using ssh2d386 from the ssh2dos
package ssh2021b,  perhaps I can help you troubleshoot.


Hi Karen!

I am using the exact same program and version.

for the record, I am not using freedos, but  the ms dos 7.10 package
mentioned on this list.
Still every day several times a day I connect  to two different servers
using  this package.


I guess your servers still run OpenSSH in versions earlier than 6.9.

may I ask again what your issue is presently?


Actually I have given up on it. I spent another day trying to get it to
work, but without success.

The problem is that I can’t connect to an Ubuntu 16.04 LTS server with
OpenSSH 7.2.

SSH2D386 gives the message:

    Expected KEX_DH_GEX_GROUP
    DH key exchange failed

The server logs:
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: kex protocol
error: type 30 seq 1 [preauth]
    Jan 27 00:02:22 ubuntu-VirtualBox sshd[2651]: error: Received
disconnect from 192.168.1.110 port 645:3: Expected KEX_DH_GEX_GRO

As I wrote I already had problems connecting to a Debian 8 server with
OpenSSH 6.7.
But there I could fix it with these lines in /etc/ssh/sshd_config on the
server.

    Ciphers aes128-cbc
    KexAlgorithms diffie-hellman-group-exchange-sha1
    MACs hmac-sha1
    HostKeyAlgorithms ssh-css

But in OpenSSH 7.2 this didn’t work.

What else did I try?

I tried to set MTU=576 in C:\FDOS\WATTCP.CFG.

I tried to recompile OpenSSH.
The first time with adding this line in in compat.c:
    { "SSHDOS*",                SSH_OLD_DHGEX },
The second time with this one:
    { "SSHDOS*",                SSH_BUG_NOREKEY|SSH_BUG_FIRSTKEX },

Both were not able to let SSH2D386 connect. It worked great with other
SSH clients.

The idea was that SSH2DOS uses code from PuTTY and there were already
several exceptions in combat.c for old PuTTY versions. The reason seems to
be that OpenSSH implemented RFC4419 and old PuTTY versions and SSH2DOS did
not. See [1], [2].

I even looked at the SSH2DOS source code. But I have no experience with
OpenWatcom. I installed it but gave up, when I saw I also had to compile
the WATT32 TCP/IP stack.

SSH2DOS uses PuTTY code, which is also Free Software. So in theory it
should be possible to replace the old PuTTY code with a more recent one.

cheers
Ulrich


[1] https://forums.red-gate.com/viewtopic.php?f=198&t=78958
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/
rfc4419.html



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Karen Lewellen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Ulrich Hansen-2

Am 28.01.2017 um 06:23 schrieb Karen Lewellen <[hidden email]>:

To answer your question for myself, I never have this issue.  No crashes, and i  can spend hours working on line.  Further I have done more than my share of downloads with sftpd386 as well.


On Fri, 27 Jan 2017, Dan Schmidt wrote:

My ssh2dos is very unstable - it usually crashes on exit or after five to
ten minutes.  Do you have this issue as well?  I am curious if I should try
a different version of DOS.


I made the same experience as Karen: I had SSH2D386 running more or less the whole morning while logged into the server. I even ran „top“ for over an hour to test the program. No crashes, no sudden exits.

Other experiences:

- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the host’s CPU by 100 percent. I limit the CPU execution cap in the VirtualBox settings to 40%, but the fan of my MacBookPro is still running constantly (but on a lower level than at 100%).

- After logging into the server, I run the command "export LANG=C“ first. Otherwise „graphical“ console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.

So far so good. Thanks to you everything is working well now.

Ulrich


.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
I didn't try the 386 version, perhaps that will be more stable.  Also, if you type "reset" before exiting, you can avoid "missing dos screen."  (IE - the crash every time I exited)  

Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several other technicians laughed at me when I bought an old Pentium for $5 saying"You can't do anything with that!" FreeDos helped me prove them wrong.

On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <[hidden email]> wrote:

Am 28.01.2017 um 06:23 schrieb Karen Lewellen <[hidden email]>:

To answer your question for myself, I never have this issue.  No crashes, and i  can spend hours working on line.  Further I have done more than my share of downloads with sftpd386 as well.


On Fri, 27 Jan 2017, Dan Schmidt wrote:

My ssh2dos is very unstable - it usually crashes on exit or after five to
ten minutes.  Do you have this issue as well?  I am curious if I should try
a different version of DOS.


I made the same experience as Karen: I had SSH2D386 running more or less the whole morning while logged into the server. I even ran „top“ for over an hour to test the program. No crashes, no sudden exits.

Other experiences:

- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the host’s CPU by 100 percent. I limit the CPU execution cap in the VirtualBox settings to 40%, but the fan of my MacBookPro is still running constantly (but on a lower level than at 100%).

- After logging into the server, I run the command "export LANG=C“ first. Otherwise „graphical“ console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.

So far so good. Thanks to you everything is working well now.

Ulrich


.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Dan Schmidt
I hope I am not committing the dreaded "forum necromancy" but I thought I might document that the 386 version, combined with the mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you for the idea.  

Also, quick type-o - "I am not sure why you would want to run SSH in DOS in VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all strange.  

On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt <[hidden email]> wrote:
I didn't try the 386 version, perhaps that will be more stable.  Also, if you type "reset" before exiting, you can avoid "missing dos screen."  (IE - the crash every time I exited)  

Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several other technicians laughed at me when I bought an old Pentium for $5 saying"You can't do anything with that!" FreeDos helped me prove them wrong.

On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <[hidden email]> wrote:

Am 28.01.2017 um 06:23 schrieb Karen Lewellen <[hidden email]>:

To answer your question for myself, I never have this issue.  No crashes, and i  can spend hours working on line.  Further I have done more than my share of downloads with sftpd386 as well.


On Fri, 27 Jan 2017, Dan Schmidt wrote:

My ssh2dos is very unstable - it usually crashes on exit or after five to
ten minutes.  Do you have this issue as well?  I am curious if I should try
a different version of DOS.


I made the same experience as Karen: I had SSH2D386 running more or less the whole morning while logged into the server. I even ran „top“ for over an hour to test the program. No crashes, no sudden exits.

Other experiences:

- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the host’s CPU by 100 percent. I limit the CPU execution cap in the VirtualBox settings to 40%, but the fan of my MacBookPro is still running constantly (but on a lower level than at 100%).

- After logging into the server, I run the command "export LANG=C“ first. Otherwise „graphical“ console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.

So far so good. Thanks to you everything is working well now.

Ulrich


.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Ulrich Hansen-2

Am 13.02.2017 um 06:19 schrieb Dan Schmidt <[hidden email]>:

I hope I am not committing the dreaded "forum necromancy“ 

I had to look that up… I really liked the picture of the ghoul in the first google result :-))

but I thought I might document that the 386 version, combined with the mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you for the idea.  

Congratulation! But as I see it, it was your idea all along. 

Also, quick type-o - "I am not sure why you would want to run SSH in DOS in VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all strange. 

Well… It kind of IS strange. ;-) The reason is simple: I have a bit time to kill at the moment, so I was taking another look at my VirtualBox/FreeDOS/Networking images I started a few years ago at https://www.lazybrowndog.net/freedos/virtualbox/. I updated them to FreeDOS 1.2 and was checking if everything still works as expected. And well, SSH2DOS wasn’t and I was unable to find a fix. So thank you again for your help!

At the moment I’m updating the MS Client pages (sigh). 



Am 13.02.2017 um 06:19 schrieb Dan Schmidt <[hidden email]>:

I hope I am not committing the dreaded "forum necromancy" but I thought I might document that the 386 version, combined with the mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you for the idea.  

Also, quick type-o - "I am not sure why you would want to run SSH in DOS in VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all strange.  

On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt <[hidden email]> wrote:
I didn't try the 386 version, perhaps that will be more stable.  Also, if you type "reset" before exiting, you can avoid "missing dos screen."  (IE - the crash every time I exited)  

Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several other technicians laughed at me when I bought an old Pentium for $5 saying"You can't do anything with that!" FreeDos helped me prove them wrong.

On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <[hidden email]> wrote:

Am 28.01.2017 um 06:23 schrieb Karen Lewellen <[hidden email]>:

To answer your question for myself, I never have this issue.  No crashes, and i  can spend hours working on line.  Further I have done more than my share of downloads with sftpd386 as well.


On Fri, 27 Jan 2017, Dan Schmidt wrote:

My ssh2dos is very unstable - it usually crashes on exit or after five to
ten minutes.  Do you have this issue as well?  I am curious if I should try
a different version of DOS.


I made the same experience as Karen: I had SSH2D386 running more or less the whole morning while logged into the server. I even ran „top“ for over an hour to test the program. No crashes, no sudden exits.

Other experiences:

- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the host’s CPU by 100 percent. I limit the CPU execution cap in the VirtualBox settings to 40%, but the fan of my MacBookPro is still running constantly (but on a lower level than at 100%).

- After logging into the server, I run the command "export LANG=C“ first. Otherwise „graphical“ console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.

So far so good. Thanks to you everything is working well now.

Ulrich


.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user
Loading...