On Mon, Aug 20, 2018 at 10:31 AM, Karen Lewellen <klewel...@shellworld.net> wrote: > really? > If sshdos no longer connects, then how am I sending this e-mail?
Karen, the point to SSH is an *encrypted* connection to the other end. Flaws have been identified in some of the commonly used encryption schemes that make them crackable and therefore insecure. I believe a TLS variant is the only currently known *secure* encryption scheme, and SSH clients and server side code are all being updated to only permit it. Connections using something else for encryption will *fail*. I don't know what you get email from/send email to, but it still accepts older deprecated encryption schemes. What will you do when it no longer does? I do *not* see SSHDOS or SSHDOS2 getting updated to support the currently mandated encryption scheme. Who would actually make the updates? > I use dos exclusively and sshdos as packaged in ssh2021b. > In the program readme file putty for windows is referenced as one element of > the various codes and libraries used in how the program was constructed. Which means they grabbed code from PuTTY as part of the SSH infrastructure. This is not the same thing as PuTTY itself. (And PuTTY is unnecessary on Linux or OS/X, as other compliant SSH solutions exist for them.) > Lastly, in the discussion area of sshdos an individual explains how they > configured sshdos to be recognized by current openssh...so > there is nothing in of itself about dOS that translates into it not > connecting. Yes, there is. See above about currently permitted encryption schemes. "Recognized by current OpenSSH" is not the same thing as being permitted to connect in an insecure manner. > granted, I am not running freedos, but I can with my dos network > configuration run a browser from my desktop if needful, it is just not > needful for me due to ssh. Whether you run FreeDOS, or a flavor like MSDOS or DR-DOS is irrelevant. What *is* relevant is that network standards are changing and DOS is being left behind because there is no one to update software for it to be compliant. At some point, sooner rather than later, your DOS based home network will no longer be *able* to connect to the outside world. What will you do then? I play with FreeDOS, and have some old DOS apps still running under Windows using vDOS Plus, but I do that for fun. The actual *work* gets done elsewhere, because it can't be *done* under DOS. I'm happy for you that DOS still meets your needs and you can do what you need to do with it. I'm just quite certain that at some point, you will no longer be able to. > Karen ______ Dennis > On Mon, 20 Aug 2018, Eric Auer wrote: > >> >>>> May be using some misinformation, >>>> but what ssh client is included in Freedos >>>> if any? >>>> Is / was there a putty dos one for example? >> >> >> Putty is a combined terminal window and SSH client, >> so it is only needed in Windows. In Linux, you use >> one of the existing Terminal windows (which seem to >> be more versatile than the command com or cmd exe >> windows of Windows) and a text-based SSH client. >> >> In DOS, you would use sshdos and ssh2dos, which are >> for two different versions of the SSH protocol. Yet, >> both are too old and no longer connect with common >> SSH server configurations! Both are text based apps. >> >> A while ago, I tried to compile a custom secure >> protocol library for a project in Linux and I can >> tell you that those things unfortunately have a >> larger number of dependencies than the should... >> >> A starting point for finding something lightweight >> and feasible to port to DOS might be this list: >> >> https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries >> >> However, that is probably more useful when you want >> to add HTTPS support to a DOS browser and less when >> you want to upgrade SSH2DOS, but I am no expert in >> those things. >> >> Regards, Eric >> >> >> >> ------------------------------------------------------------------------------ >> 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 -- ______ Dennis https://plus.google.com/u/0/105128793974319004519 ------------------------------------------------------------------------------ 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
