Good call out. I trust that Al will want to make this right with you.

-L

On Wed, Apr 29, 2026 at 9:51 AM Michael Brutman via Freedos-user <
[email protected]> wrote:

> On a slightly related note ...
>
> I'm a little concerned about these changes to SSH2DOS
>
>    - My UTF-8 code is GPL3 in the mTCP project.  SSH2DOS is GPL2.  The
>    two licenses are incompatible.  Al just says "Original mTCP code is GPLv3.
>    This port maintains the same license", but you can't just hand-wave that
>    incompatible license problem away.  His fork now has at least a license
>    violation, possibly more depending on the Claude generated stuff.  That can
>    be fixed, but it's not completely legit as it is right now.
>    - Al stripped out the ability to define arbitrary mappings between
>    unicode code points and MSDOS code pages via text files, which is one of
>    the big features of the original code.  This is a regression.
>    - While the mTCP source is acknowledged, there is not a link to it
>    anywhere.  That's also a no-no when reusing open source.  It should mention
>    the original soure of the code in case somebody wants to try to keep it in
>    sync.
>    - I'm not thrilled about having the UTF-8 changes lumped into the same
>    change as Claude (AI) generated code.  They should have been committed
>    separately to make it clear what human/system generated what code.
>
> I'll try to bring these issues up with Al, but be aware that they exist.
>
>
> Mike
>
> On Wed, Apr 29, 2026 at 8:00 AM Michael Brutman <[email protected]>
> wrote:
>
>> There should be no conflict between mTCP and other networking programs.
>> The only exception is if NetDrive is loaded; WATTCP programs probably don't
>> like the fake packet driver that NetDrive presents. (Fixing that is on the
>> to-do list.)
>>
>> What exactly were you seeing that makes you think there is a conflict?
>>
>> Side note: The UTF-8 code for Al's was adapted from my mTCP code.
>>
>>
>>
>> On Wed, Apr 29, 2026, 04:05 hollow-one via Freedos-user <
>> [email protected]> wrote:
>>
>>> That's very cool, does it work with MTCP?
>>>
>>> I found some programs using WatTCP/32 work and some colide with MTCP
>>> suite from Michael Brutman, thus asking.
>>>
>>> -h1
>>> On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
>>>
>>> Hi, is there a compiled version?
>>> The only file available for download is from 2021.
>>> At least I couldn't find the latest version.
>>>
>>> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
>>> [email protected]) escribió:
>>>
>>>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>>>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>>>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>>>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>>>> DH, AES, and SHA256).
>>>>
>>>> https://github.com/ajrossnz/ssh2dos
>>>> https://github.com/Toyoyo/ssh2dos
>>>> https://github.com/AnttiTakala/SSH2DOS
>>>> https://sshdos.sourceforge.net/
>>>> _______________________________________________
>>>> Freedos-user mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>>
>>>
>>>
>>> _______________________________________________
>>> Freedos-user mailing 
>>> [email protected]https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>> _______________________________________________
>>> Freedos-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>> _______________________________________________
> Freedos-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to