[prev in list] [next in list] [prev in thread] [next in thread]
List: freedos-user
Subject: Re: [Freedos-user] New mTCP available
From: Dan Schmidt <helpdeskdan () gmail ! com>
Date: 2022-07-16 20:41:17
Message-ID: CADQwR9UPs6xuMzDW9QLcFkwgKOrqhTbjtPmoBcVgXFZzB5XD6g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks all for your comments, I'm aware of the ssh2dos project and
suggested noise.sys to help with security.
I'm glad to hear Unicode in mTCP Telnet is on the table and would like to
thank Mike for his continued work. (PC fished from trash + FreeDos + mTCP
Telnet = quick, cheap terminal for lab use)
On Sat, Jul 16, 2022 at 11:46 AM Louis Santillan <lpsantil@gmail.com> wrote:
> It was mentioned recently that ssh2dos was updated last year to include
> the newer protocols.
>
>
> https://github.com/AnttiTakala/SSH2DOS
>
> Would be awesome to see if mTCP improved the networking throughput or
> latency.
>
> At some point I'd love sit down and try to get the mTCP ported to djgpp
> but the last time I tried I was having issues managing the buffer space in
> and out of the lower 1MB.
>
>
>
> On Sat, Jul 16, 2022 at 2:49 AM Liam Proven <lproven@gmail.com> wrote:
>
>> On Sat, 16 Jul 2022 at 01:13, Michael Brutman <mbbrutman@brutman.com>
>> wrote:
>>
>> > Computationally, SSH is not feasible on the 16 bit machines that I
>> target for this project.
>> > Even with enough compute power, you need to find DOS equivalents of all
>> of the libraries. Which includes the ciphers, key exchanges, etc. And
>> then you need to port those, and what they depend on to DOS. Without
>> introducing security holes.
>> > SSH ciphers are a moving target. What is acceptable today will be
>> deprecated in a few years. It is difficult to keep up.
>>
>> Agreed. Modern cryptography is one of the relatively few things that uses
>> the large amount of bandwidth of modern CPUs.
>>
>> It's possible to run older versions of OpenBSD on 30+ year old DEC
>> minicomputers, for example. It was dropped only because Theo de Raadt
>> couldn't get modern VAXstation hardware to compile it on. I tried to
>> donate a VAXstation 4000/90 to the project when I emigrated -- Red Hat was
>> going to ship it to Canada from the UK for me.
>>
>> De Raadt changed his mind when he learned it wasn't the fastest model,
>> and Red Hat Farnborough lost the machine. 😡
>>
>> Anyway, making new SSH keys on a VAX took as much as a couple of *days*
>> in some instances.
>>
>> --
>> Liam Proven ~ Profile: https://about.me/liamproven
>> Email: lproven@cix.co.uk ~ gMail/gTalk/FB: lproven@gmail.com
>> Twitter/LinkedIn: lproven ~ Skype: liamproven
>> UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420)
>> 702-829-053
>> _______________________________________________
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
[Attachment #5 (text/html)]
<div dir="ltr"><div>Thanks all for your comments, I'm aware of the ssh2dos \
project and suggested noise.sys to help with security. \
<br></div><div><br></div><div>I'm glad to hear Unicode in mTCP Telnet is on the \
table and would like to thank Mike for his continued work. (PC fished from trash + \
FreeDos + mTCP Telnet = quick, cheap terminal for lab use)<br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 16, 2022 at 11:46 \
AM Louis Santillan <<a href="mailto:lpsantil@gmail.com">lpsantil@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">It was \
mentioned recently that ssh2dos was updated last year to include the newer \
protocols.</div><div dir="auto"><br></div><div dir="auto"><div \
dir="auto"><br></div><div><a href="https://github.com/AnttiTakala/SSH2DOS" \
target="_blank">https://github.com/AnttiTakala/SSH2DOS</a></div><br></div><div \
dir="auto">Would be awesome to see if mTCP improved the networking throughput or \
latency.</div><div dir="auto"><br></div><div dir="auto">At some point I'd love sit \
down and try to get the mTCP ported to djgpp but the last time I tried I was having \
issues managing the buffer space in and out of the lower 1MB.</div><div \
dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Sat, Jul 16, 2022 at 2:49 AM Liam Proven <<a \
href="mailto:lproven@gmail.com" target="_blank">lproven@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">On Sat, \
16 Jul 2022 at 01:13, Michael Brutman <<a href="mailto:mbbrutman@brutman.com" \
target="_blank">mbbrutman@brutman.com</a>> wrote:<br><br><div>> \
Computationally, SSH is not feasible on the 16 bit machines that I target for this \
project.<br>> Even with enough compute power, you need to find DOS equivalents of \
all of the libraries. Which includes the ciphers, key exchanges, etc. And then \
you need to port those, and what they depend on to DOS. Without introducing \
security holes.<br>> SSH ciphers are a moving target. What is acceptable today \
will be deprecated in a few years. It is difficult to keep up.<br><br>Agreed. \
Modern cryptography is one of the relatively few things that uses the large amount \
of bandwidth of modern CPUs. </div><div><br></div><div>It's possible to run \
older versions of OpenBSD on 30+ year old DEC minicomputers, for example. It was \
dropped only because Theo de Raadt couldn't get modern VAXstation hardware to \
compile it on. I tried to donate a VAXstation 4000/90 to the project when I \
emigrated -- Red Hat was going to ship it to Canada from the UK for \
me.</div><div><br></div><div>De Raadt changed his mind when he learned it wasn't \
the fastest model, and Red Hat Farnborough lost the machine. 😡<br><br>Anyway, \
making new SSH keys on a VAX took as much as a couple of *days* in some \
instances.</div></div><div dir="ltr"><div> <br>-- <br>Liam Proven ~ Profile: <a \
href="https://about.me/liamproven" \
target="_blank">https://about.me/liamproven</a><br>Email: <a \
href="mailto:lproven@cix.co.uk" target="_blank">lproven@cix.co.uk</a> ~ \
gMail/gTalk/FB: <a href="mailto:lproven@gmail.com" \
target="_blank">lproven@gmail.com</a><br>Twitter/LinkedIn: lproven ~ Skype: \
liamproven<br>UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) \
702-829-053</div></div> _______________________________________________<br>
Freedos-user mailing list<br>
<a href="mailto:Freedos-user@lists.sourceforge.net" \
target="_blank">Freedos-user@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/freedos-user" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user</a><br> \
</blockquote></div></div> _______________________________________________<br>
Freedos-user mailing list<br>
<a href="mailto:Freedos-user@lists.sourceforge.net" \
target="_blank">Freedos-user@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/freedos-user" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user</a><br> \
</blockquote></div>
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic