We did talk at length about it almost exactly a year ago. The tldr version
is that you would need ssh2d386 and you have to have access to modify the
ssh config on the server to support older ciphers. All my attempts to get
a decent C coder interested in updating the project have failed.
https://sourceforge.net/p/freedos/mailman/message/35629497/
On Sun, Dec 31, 2017 at 11:57 PM, Rugxulo <rugx...@gmail.com> wrote:
> Hi,
>
> On Sun, Dec 31, 2017 at 5:27 PM, Jerome Shidel <jer...@shidel.net> wrote:
> >
> > Anyhow, I recall seeing a thread earlier discussing something similar.
> At least, I think it was similar.
> > I was not very interested at the time and kinda only skimmed it. But, if
> I remember what I half glimpsed,
> > it involved something about having to add some older protocols to the
> server. But, I’m probably mis-remembering it.
> >
> > Sorry, I really can’t be much more help than that.
>
> I'm a networking noob overall, but ....
>
> Wasn't something like this discussed earlier this year, mainly by
> Ulrich Hansen? A quick search of my email archives shows a few
> messages from him about it.
>
> So maybe wait for him to chime in. (Or email him privately? Or just
> search the mailing list archives for it.)
>
> ------------------------------------------------------------
> ------------------
> 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
> Freedos-user@lists.sourceforge.net
> 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
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
