Yes, and if you read that discussion about open ssh, you will find the
person also found a solution.
It is part of how shellworld allows me here, and shellworld uses a more
current edition of openssh than dreamhost.
ssh may have moved on in 12 years, but while there are options the aspect
of my body requiring my set up have not, with the synthesis I use computer
wise getting worse in other platforms
not better .
sshdos is open source now which is why I hinted my best door might be
getting it updated. The dhpgg options have already been discussed.
still Mike points out that dreamhost should still let my key in, making it
less about the program and more about something else.
On Thu, 4 Oct 2018, Lennart Sorensen wrote:
On Wed, Oct 03, 2018 at 03:50:14PM -0400, Karen Lewellen via talk wrote:
Hi again,
I am not using windows either, but DOS.
The program, sshdos, was created by someone involved with the freedos
project, which is still under development.
When I use the program to ssh telnet well anywhere, and run the -v option I
witness the exchange process, when it works like here and when it does not.
The program was compiled using some parts of putty for windows yes, along
with some Linux libraries.
Proof it works, I am using it to write this e-mail.
But as expressed my host here shellworld is a small enough company to work
with me.
Djgpp is another dos project which includes some more up to date keys. I
believe my best option is going to be discovering if there is either another
DOS ssh client, the speech and screen readers for Linux directly all use
voices that stimulate my brain's dizzy centres, or seek to upgrade sshdos
since the code is open source.
Thanks for the firm information about the keys I am using.
Happy thanksgiving to the list,
Kare
Well sshdos (useless since it is protocol 1.5) and ssh2dos (protocol 2.0)
look pretty close to useless by now. Last update to ssh2dos was in 2006.
ssh and security has moved on in the last 12 years.
For example last yearh people were having issues
connecting to new openssh versions with it:
http://freedos.10956.n7.nabble.com/Some-struggle-with-SSH2DOS-solved-td25894.html
Openssh simply doesn't allow the outdated key methods that ancient ssh
client wants anymore because they have been found to be insecure.
But I see you were part of that discussion so you already know about
those problems.
I guess freedos could use an updated ssh client.
--
Len Sorensen
---
Talk Mailing List
[email protected]
https://gtalug.org/mailman/listinfo/talk
