Quantcast

Some struggle with SSH2DOS (solved)

classic Classic list List threaded Threaded
32 messages Options
12
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

Karen Lewellen-2
In reply to this post by Ulrich Hansen-2
From: Ulrich Hansen <[hidden email]>


--===============1286602081422601077==
Content-Type: multipart/alternative;
        boundary="Apple-Mail=_FB62985E-3376-4E71-8B37-98EBAD86AAFE"


--Apple-Mail=_FB62985E-3376-4E71-8B37-98EBAD86AAFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
        charset=utf-8

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]
<mailto:[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]
<mailto:[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]
<mailto:[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]
<mailto:[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]
<mailto:[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 canrCOt 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 didnrCOt 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
<https://forums.red-gate.com/viewtopic.php?f=198&t=78958>
> [2] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/
<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
<http://sdm.link/slashdot>
> _______________________________________________
> Freedos-user mailing list
> [hidden email] <mailto:[hidden email]>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<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
<http://sdm.link/slashdot>
> _______________________________________________
> Freedos-user mailing list
> [hidden email] <mailto:[hidden email]>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<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
<http://sdm.link/slashdot>
> _______________________________________________
> Freedos-user mailing list
> [hidden email] <mailto:[hidden email]>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<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


--Apple-Mail=_FB62985E-3376-4E71-8B37-98EBAD86AAFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
        charset=utf-8

<html><head><meta http-equiv="Content-Type" content="text/html
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;" class=""><div class="">Wow. I am
stunned. This has solved the problem. I have spent more than a day searching
for such a solution.</div><div class=""><br class=""></div><div class="">I am
now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2</div><div
class="">Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos
with "FDNPKG install ssh2dos"</div><div class=""><br class=""></div><div
class="">Thank you very, very much!</div><div class=""><br class=""></div><div
class="">Ulrich</div><div class=""><br class=""></div><div class=""><br
class=""></div><br class=""><div><blockquote type="cite" class=""><div
class="">Am 27.01.2017 um 06:39 schrieb Dan Schmidt &lt;<a
href="mailto:[hidden email]" class="">[hidden email]</a>&gt;:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I forgot - you may need to regenerate your keys with "ssh-keygen -A" after modifying the server.&nbsp;</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt <span dir="ltr" class="">&lt;<a href="mailto:[hidden email]" target="_blank" class="">[hidden email]</a>&gt;</span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue?&nbsp;<div class=""><br class="">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.&nbsp; Using a token based login, such as google-authenticator,
may be advisable if your server is public facing. &nbsp;</div><div class=""><br class=""></div><div class="">Firstly, add this to your server's&nbsp;<span style="" class="">/etc/ssh/sshd_config:</span><br class=""><br class="">KexAlgorithms diffie-hellman-group1-sha1,<a href="mailto:[hidden email]" target="_blank" class="">cur<wbr class="">[hidden email]</a>,<wbr class="">ecdh-sha2-nistp256,ecdh-sha2-<wbr class="">nistp384,ecdh-sha2-nistp521,<wbr class="">diffie-hellman-group-exchange-<wbr class="">sha256,diffie-hellman-group14-<wbr class="">sha1<br class="">Ciphers 3des-cbc,blowfish-cbc,aes128-<wbr class="">cbc,aes128-ctr,aes256-ctr<br class="">HostKeyAlgorithms +ssh-dss<br class=""><br class="">Then, make use of the -g option - it goes BEFORE your username in ssh2dos.&nbsp; You should now be able to connect. &nbsp;</div><div class=""><br class="">I do not know why simply adding +diffie-hellman-group1-sha1 doesn't work, it seems it should.&nbsp; Also, I was
in a rush - I may be excluding some newer options - report back if you find/add them with success.&nbsp;</div><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">-Dan</div></font></span></div><div class="gmail_extra"><br class=""><div class="gmail_quote"><div class=""><div class="h5">On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <span dir="ltr" class="">&lt;<a href="mailto:[hidden email]" target="_blank" class="">[hidden email]</a>&gt;</span> wrote:<br class=""></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="h5">Hi Bill,<br class="">
While I appreciate your desire for wisdom, I feel rather sure&nbsp; my specific
situation will not apply to anyone else here most likely.<br class="">
I use ssh2d386 to&nbsp; access at least one commercial shell, but those shell
services are maintained by others.&nbsp; I am not for example accessing my own
server.<br class="">
If the servers you desire reaching are run by other people,&nbsp; give me an
example and I will try.<br class="">
If my many years of computing has taught me anything is that the word
Personal&nbsp; is important for a reason.<br class="">
Kare<div class="m_-2658655359570531662HOEnZb"><div
class="m_-2658655359570531662h5"><br class="">
<br class="">
<br class="">
On Thu, 26 Jan 2017, William Dudley wrote:<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Karen,<br class="">
<br class="">
If you know how to get ssh2d386 to connect to a modern openssh, as on<br
class="">
Ubuntu 16.04,<br class="">
please share the recipe with us!<br class="">
<br class="">
Thanks,<br class="">
Bill Dudley<br class="">
<br class="">
<br class="">
This email is free of malware because I run Linux.<br class="">
<br class="">
On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen &lt;<a
href="mailto:[hidden email]" target="_blank"
class="">[hidden email]</a>&gt;<br class="">
wrote:<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Well, if you have given up no point in my sharing.<br class="">
We use the same edition of Ubuntu, both with dreamhost who has my office,<br
class="">
and here at shellworld.<br class="">
While the latter requires me to make use of a few ssh2021b options, the -g<br
class="">
option&nbsp; for example, I encounter no issues.<br class="">
I am going to guess that&nbsp; things like machine speed, mine is a p3 with<br
class="">
allot of memory, impacts your situation.<br class="">
nor, I would hope, your&nbsp; location in the world.<br class="">
Sorry I did not notice your post before you abandoned&nbsp; the effort.<br
class="">
Kare<br class="">
<br class="">
<br class="">
<br class="">
On Fri, 27 Jan 2017, Ulrich Hansen wrote:<br class="">
<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Am 26.01.2017 um 18:19 schrieb Karen Lewellen &lt;<a
href="mailto:[hidden email]" target="_blank"
class="">[hidden email]</a>&gt;:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br class="">
As I am presently writing this e-mail using ssh2d386 from the ssh2dos<br
class="">
package ssh2021b,&nbsp; perhaps I can help you troubleshoot.<br class="">
<br class="">
</blockquote>
<br class="">
Hi Karen!<br class="">
<br class="">
I am using the exact same program and version.<br class="">
<br class="">
for the record, I am not using freedos, but&nbsp; the ms dos 7.10 package<br
class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
mentioned on this list.<br class="">
Still every day several times a day I connect&nbsp; to two different servers<br
class="">
using&nbsp; this package.<br class="">
<br class="">
</blockquote>
<br class="">
I guess your servers still run OpenSSH in versions earlier than 6.9.<br
class="">

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
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-2
In reply to this post by Ulrich Hansen-2
From: Dan Schmidt <[hidden email]>

--===============5135558072373083799==
Content-Type: multipart/alternative; boundary=f403045fc1c842840405471fe722

--f403045fc1c842840405471fe722
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 canrCOt 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 didnrCOt 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://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://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://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://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
>
>

--f403045fc1c842840405471fe722
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir="ltr">I am equally as stunned - I will remember this day as the day I
tried to help somebody on the internet and they said &quot;thank you&quot;
instead of flaming or ignoring me.-a<div><br></div><div>My ssh2dos is very
unstable - it usually crashes on exit or after five to ten minutes.-a Do you
have this issue as well?-a I am curious if I should try a different version of
DOS. -a</div></div><div class="gmail_extra"><br><div class="gmail_quote">On
Fri, Jan 27, 2017 at 12:04 AM, Ulrich Hansen <span dir="ltr">&lt;<a
href="mailto:[hidden email]" target="_blank">[hidden email]</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Wow. I am stunned. This has solved the problem. I have spent more than a day searching for such a solution.</div><div><br></div><div>I am now able to log into a Ubuntu 16.04 LTS server with OpenSSH 7.2</div><div>Client is a fresh install of FreeDOS 1.2 where I installed ssh2dos with &quot;FDNPKG install ssh2dos&quot;</div><div><br></div><div>Thank you very, very much!</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Ulrich</div></font></span><div><div class="h5"><div><br></div><div><br></div><br><div><blockquote type="cite"><div>Am 27.01.2017 um 06:39 schrieb Dan Schmidt &lt;<a href="mailto:[hidden email]" target="_blank">[hidden email]</a>&gt;:</div><br class="m_7138243259445314162Apple-interchange-newline"><div><div
 dir="ltr">I forgot - you may need to regenerate your keys with &quot;ssh-keygen -A&quot; after modifying the server.-a</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 26, 2017 at 10:38 PM, Dan Schmidt <span dir="ltr">&lt;<a href="mailto:[hidden email]" target="_blank">[hidden email]</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I am unsure what it is that makes ssh2dos so unstable for me - nobody else has this issue?-a<div><br>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.-a Using a token based login, such as google-authenticator, may be advisable if your server is public facing. -a</div><div><br></div><div>Firstly, add this to your server&#39;s-a<span>/etc/ssh/sshd_config:</span><br><br>KexAlgorithms diffie-hellman-group1-sha1,<a href="m
ailto:[hidden email]" target="_blank">cur<wbr>[hidden email]</a>,ecdh<wbr>-sha2-nistp256,ecdh-sha2-nistp<wbr>384,ecdh-sha2-nistp521,diffie-<wbr>hellman-group-exchange-sha256,<wbr>diffie-hellman-group14-sha1<br>Ciphers 3des-cbc,blowfish-cbc,aes128-c<wbr>bc,aes128-ctr,aes256-ctr<br>HostKeyAlgorithms +ssh-dss<br><br>Then, make use of the -g option - it goes BEFORE your username in ssh2dos.-a You should now be able to connect. -a</div><div><br>I do not know why simply adding +diffie-hellman-group1-sha1 doesn&#39;t work, it seems it should.-a Also, I was in a rush - I may be excluding some newer options - report back if you find/add them with success.-a</div><span class="m_7138243259445314162HOEnZb"><font color="#888888"><div><br></div><div>-Dan</div></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_7138243259445314162h5">On Thu, Jan 26, 2017 at 9:42 PM, Karen Lewellen <span dir="ltr">&lt;<a href="mailto:klewellen@shellwo
rld.net" target="_blank">[hidden email]</a>&gt;</span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_7138243259445314162h5">Hi Bill,<br>
While I appreciate your desire for wisdom, I feel rather sure-a my specific
situation will not apply to anyone else here most likely.<br>
I use ssh2d386 to-a access at least one commercial shell, but those shell
services are maintained by others.-a I am not for example accessing my own
server.<br>
If the servers you desire reaching are run by other people,-a give me an
example and I will try.<br>
If my many years of computing has taught me anything is that the word
Personal-a is important for a reason.<br>
Kare<div class="m_7138243259445314162m_-2658655359570531662HOEnZb"><div
class="m_7138243259445314162m_-2658655359570531662h5"><br>
<br>
<br>
On Thu, 26 Jan 2017, William Dudley wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Karen,<br>
<br>
If you know how to get ssh2d386 to connect to a modern openssh, as on<br>
Ubuntu 16.04,<br>
please share the recipe with us!<br>
<br>
Thanks,<br>
Bill Dudley<br>
<br>
<br>
This email is free of malware because I run Linux.<br>
<br>
On Thu, Jan 26, 2017 at 9:10 PM, Karen Lewellen &lt;<a
href="mailto:[hidden email]" target="_blank">[hidden email]</a>&gt;<br>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Well, if you have given up no point in my sharing.<br>
We use the same edition of Ubuntu, both with dreamhost who has my office,<br>
and here at shellworld.<br>
While the latter requires me to make use of a few ssh2021b options, the -g<br>
option-a for example, I encounter no issues.<br>
I am going to guess that-a things like machine speed, mine is a p3 with<br>
allot of memory, impacts your situation.<br>
nor, I would hope, your-a location in the world.<br>
Sorry I did not notice your post before you abandoned-a the effort.<br>
Kare<br>
<br>
<br>
<br>
On Fri, 27 Jan 2017, Ulrich Hansen wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Am 26.01.2017 um 18:19 schrieb Karen Lewellen &lt;<a
href="mailto:[hidden email]" target="_blank">[hidden email]</a>&gt;:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
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
In reply to this post by Ulrich Hansen-2
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

Karen Lewellen-2
In reply to this post by Ulrich Hansen-2
From: Karen Lewellen <[hidden email]>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1404930036-1557067193-1485581000=:14597
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

I am so happy you could help him!
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.
Kare


On Fri, 27 Jan 2017, Dan Schmidt wrote:

> 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 canrCOt 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 didnrCOt 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://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://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://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://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
>>
>>
>
---1404930036-1557067193-1485581000=:14597
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
---1404930036-1557067193-1485581000=:14597
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user

---1404930036-1557067193-1485581000=:14597--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
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
In reply to this post by Karen Lewellen

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

Karen Lewellen-2
In reply to this post by Ulrich Hansen-2
From: Dan Schmidt <[hidden email]>

--===============5733539331453050794==
Content-Type: multipart/alternative; boundary=001a114057c24860b105475c76bb

--001a114057c24860b105475c76bb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 rCRtoprCL 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 hostrCOs 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=CrCL first.
> Otherwise rCRgraphicalrCL 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
>
>

--001a114057c24860b105475c76bb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir="ltr">I didn&#39;t try the 386 version, perhaps that will be more
stable.-a Also, if you type &quot;reset&quot; before exiting, you can avoid
&quot;missing dos screen.&quot; -a(IE - the crash every time I exited)
-a<div><br></div><div>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. -a:-)
-aYears ago, several other technicians laughed at me when I bought an old
Pentium for $5 saying&quot;You can&#39;t do anything with that!&quot; FreeDos
helped me prove them wrong.</div></div><div class="gmail_extra"><br><div
class="gmail_quote">On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <span
dir="ltr">&lt;<a href="mailto:[hidden email]"
target="_blank">[hidden email]</a>&gt;</span> wrote:<br><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span
class=""><blockquote type="cite"><div>Am 28.01.2017 um 06:23 schrieb Karen
Lewellen &lt;<a href="mailto:[hidden email]"
target="_blank">[hidden email]</a>&gt;:</div><div><br
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">To answer your question for myself, I never have this issue.-a No crashes, and i -acan spend hours working on line.-a Further I have done more than my share of downloads with sftpd386 as well.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></blockquote><div><br></div><div><br></div></span><blockquote type="cite"><div><span class=""
><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">On Fri, 27 Jan 2017, Dan Schmidt wrote:</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></span><span class=""><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>My ssh2dos is very unstable - it usually crashes on exit or after five to<br>ten minutes.-a Do you have this issue as well?-a I am curious if I should try<br>a different version of DOS.<br></blockquote
></span></div></blockquote></div><div><br></div><div><br></div><div>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 rCRtoprCL for over an hour to test the program. No crashes, no sudden exits.</div><div><br></div><div>Other experiences:</div><div><br></div><div>- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the hostrCOs 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%).</div><div><br></div><div>- After logging into the server, I run the command &quot;export LANG=CrCL first. Otherwise rCRgraphicalrCL console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.</div><div><br></div><div>So far so good. Thanks to you everything is working well now.</div><div><br></div><div>Ulrich</div><div><br></div><div><br><
/div><div>.</div><div><br></div><div><br></div></div><br>------------------------------<wbr>------------------------------<wbr>------------------<br>
Check out the vibrant tech community on one of the world&#39;s most<br>
engaging tech sites, SlashDot.org! <a href="http://sdm.link/slashdot"
rel="noreferrer" target="_blank">http://sdm.link/slashdot</a><br>______________________________<wbr>_________________<br>
Freedos-user mailing list<br>
<a href="mailto:[hidden email]">Freedos-user@lists.<wbr>sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/freedos-user"
rel="noreferrer" target="_blank">https://lists.sourceforge.net/<wbr>lists/listinfo/freedos-user</a><br>
<br></blockquote></div><br></div>

--001a114057c24860b105475c76bb--


--===============5733539331453050794==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===============5733539331453050794==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Freedos-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===============5733539331453050794==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
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
In reply to this post by Ulrich Hansen-2
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SSH2DOS - no connection with recent servers

Karen Lewellen-2
In reply to this post by Ulrich Hansen-2
From: Ulrich Hansen <[hidden email]>


--===============0481829807500901100==
Content-Type: multipart/alternative;
        boundary="Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36"


--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
        charset=utf-8


> Am 13.02.2017 um 06:19 schrieb Dan Schmidt <[hidden email]
<mailto:[hidden email]>>:
>
> I hope I am not committing the dreaded "forum necromancyrCL

I had to look that uprCa 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.

WellrCa 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/
<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
wasnrCOt and I was unable to find a fix. So thank you again for your help!

At the moment IrCOm 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]
<mailto:[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]
<mailto:[hidden email]>> wrote:
>
>> Am 28.01.2017 um 06:23 schrieb Karen Lewellen <[hidden email]
<mailto:[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 rCRtoprCL 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 hostrCOs 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=CrCL first.
Otherwise rCRgraphicalrCL 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
<http://sdm.link/slashdot>
> _______________________________________________
> Freedos-user mailing list
> [hidden email] <mailto:[hidden email]>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<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


--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
        charset=utf-8

<html><head><meta http-equiv="Content-Type" content="text/html
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;" class=""><div class=""><br
class=""></div><div class=""><div class=""><blockquote type="cite"
class=""><div class="">Am 13.02.2017 um 06:19 schrieb Dan Schmidt &lt;<a
href="mailto:[hidden email]" class="">[hidden email]</a>&gt;:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I hope I am not committing the dreaded "forum necromancyrCL&nbsp;</div></div></blockquote><div class=""><br class=""></div><div class="">I had to look that uprCa I really liked the picture of the ghoul in the first google result :-))</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">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. &nbsp;</div></div></blockquote><div class=""><br class=""></div>Congratulation! But as I see it, it was your idea all along.&nbsp;<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Also, quick type-o - "I am not sure why you would want to&nbsp;<i class="">run SSH</i>&nbsp;
in DOS in VirtualBox" &nbsp;I did not mean to imply that running Dos on VirtualBox is at all strange.&nbsp;</div></div></div></blockquote><div class=""><br class=""></div>WellrCa 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&nbsp;<a href="https://www.lazybrowndog.net/freedos/virtualbox/" class="">https://www.lazybrowndog.net/freedos/virtualbox/</a>. I updated them to FreeDOS 1.2 and was checking if everything still works as expected. And well, SSH2DOS wasnrCOt and I was unable to find a fix. So thank you again for your help!</div><div class=""><br class=""></div><div class="">At the moment IrCOm updating the MS Client pages (sigh).&nbsp;</div></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">Am 13.02.2017 um 06:19 schrieb Dan Schmidt &lt;<a href="mailto:he
[hidden email]" class="">[hidden email]</a>&gt;:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">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. &nbsp;<div class=""><br class=""></div><div class="">Also, quick type-o - "I am not sure why you would want to <i class="">run SSH</i> in DOS in VirtualBox" &nbsp;I did not mean to imply that running Dos on VirtualBox is at all strange. &nbsp;</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt <span dir="ltr" class="">&lt;<a href="mailto:[hidden email]" target="_blank" class="">[hidden email]</a>&gt;</span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" clas
s="">I didn't try the 386 version, perhaps that will be more stable.&nbsp; Also, if you type "reset" before exiting, you can avoid "missing dos screen." &nbsp;(IE - the crash every time I exited) &nbsp;<div class=""><br class=""></div><div class="">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. &nbsp;:-) &nbsp;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.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote"><div class=""><div class="h5">On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <span dir="ltr" class="">&lt;<a href="mailto:[hidden email]" target="_blank" class="">[hidden email]</a>&gt;</span> wrote:<br class=""></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="h5"><
div style="word-wrap:break-word" class=""><br class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">Am 28.01.2017 um 06:23 schrieb Karen Lewellen &lt;<a href="mailto:[hidden email]" target="_blank" class="">[hidden email]</a>&gt;:</div><div class=""><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">To answer your question for myself, I never have this issue.&nbsp; No crashes, and i &nbsp;can spend hours working on line.&nbsp; Further I have done more than my share of downloads with sftpd386 a
s well.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div></span><blockquote type="cite" class=""><div class=""><span class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">On Fri, 27 Jan 2017, Dan Schmidt wrote:</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""></span><span class=""><blockquote type="cite" style="
font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><br class="">My ssh2dos is very unstable - it usually crashes on exit or after five to<br class="">ten minutes.&nbsp; Do you have this issue as well?&nbsp; I am curious if I should try<br class="">a different version of DOS.<br class=""></blockquote></span></div></blockquote></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">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 rCRtoprCL for over an hour to test the program. No crashes, no sudden exits.</div><div class=""><br class=""></div><div class="">Other experiences:</div><div class=""><br class=""></div><div class="">- As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does use the h
ostrCOs 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%).</div><div class=""><br class=""></div><div class="">- After logging into the server, I run the command "export LANG=CrCL first. Otherwise rCRgraphicalrCL console programs like midnight commander or dpkg-reconfigure will show wrong characters in SSH2DOS.</div><div class=""><br class=""></div><div class="">So far so good. Thanks to you everything is working well now.</div><div class=""><br class=""></div><div class="">Ulrich</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">.</div><div class=""><br class=""></div><div class=""><br class=""></div></div><br class=""></div></div>------------------------------<wbr class="">------------------------------<wbr class="">------------------<span class=""><br class="">
Check out the vibrant tech community on one of the world's most<br class="">
engaging tech sites, <a href="http://slashdot.org" class="">SlashDot.org</a>!
<a href="http://sdm.link/slashdot" rel="noreferrer" target="_blank"
class="">http://sdm.link/slashdot</a><br
class="">______________________________<wbr class="">_________________<br
class="">
Freedos-user mailing list<br class="">
<a href="mailto:[hidden email]" target="_blank"
class="">[hidden email]<wbr class="">.net</a><br class="">
<a href="https://lists.sourceforge.net/lists/listinfo/freedos-user"
rel="noreferrer" target="_blank" class="">https://lists.sourceforge.net/<wbr
class="">lists/listinfo/freedos-user</a><br class="">
<br class=""></span></blockquote></div><br class=""></div>
</blockquote></div><br class=""></div>
------------------------------------------------------------------------------<br class="">Check out the vibrant tech community on one of the world's most<br class="">engaging tech sites, <a href="http://slashdot.org" class="">SlashDot.org</a>! <a href="http://sdm.link/slashdot_______________________________________________" class="">http://sdm.link/slashdot_______________________________________________</a><br class="">Freedos-user mailing list<br class=""><a href="mailto:[hidden email]" class="">[hidden email]</a><br class="">https://lists.sourceforge.net/lists/listinfo/freedos-user<br class=""></div></blockquote></div><br class=""></body></html>
--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36--


--===============0481829807500901100==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===============0481829807500901100==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
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
12
Loading...