[mosh-devel] Including Mosh in our Software

[Alan Kim]

Noted. Thank you!

Appreciate the quick response, Keith.

Regards,

*Alan Kim *| NetSarang, Inc. | Director of Sales & Marketing
4701 Patrick Henry Dr. BLDG 22 Suite 137, Santa Clara, CA 95054, U.S.A.

Tel: (669) 204-3301 | Email: alan at netsarang.com | Website: www.netsarang.com


*FACEBOOK: *http://facebook.com/netsarang
<https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/facebook-com-netsarang>
 | *TWITTER**: *http://twitter.com/netsarang
<https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/twitter-com-netsarang>



On Tue, Jan 4, 2022 at 9:11 AM Keith Winstein <keithw at mit.edu> wrote:

> Nobody has an exemption. My understanding was that JuiceSSH distributes a
> mosh-client executable and just invokes it.
>
> On Tue, Jan 4, 2022 at 6:24 AM Alan Kim <alan at netsarang.com> wrote:
>
>> Hi Keith,
>>
>> Thank you for the information.
>>
>> According to GPL licensing, all code linked with GPL source code must be
>> disclosed under a GPL compatible license.
>> However, several software products which are similar to ours all have
>> Mosh included, but do not seem to follow this rule. (Mobaxterm, Termius,
>> JuiceSSH to name a few). Do they have some kind of special exemption?
>>
>> I'd appreciate any advice you can provide. Thank you!
>>
>> Regards,
>>
>> *Alan Kim *| NetSarang, Inc. | Director of Sales & Marketing
>> 4701 Patrick Henry Dr. BLDG 22 Suite 137, Santa Clara, CA 95054, U.S.A.
>>
>> Tel: (669) 204-3301 | Email: alan at netsarang.com | Website:
>> www.netsarang.com
>>
>>
>> *FACEBOOK: *http://facebook.com/netsarang
>> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/facebook-com-netsarang>
>>  | *TWITTER**: *http://twitter.com/netsarang
>> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/twitter-com-netsarang>
>>
>>
>>
>> On Wed, Dec 15, 2021 at 11:35 PM Keith Winstein <keithw at mit.edu> wrote:
>>
>>> Hello,
>>>
>>> Thank you for your inquiry. Mosh is free software, licensed under the
>>> GNU GPL. The requirements would be similar to those of Linux, Git, GCC,
>>> Emacs, OpenJDK, Blender, GIMP, VLC, Wordpress, etc. You are welcome to
>>> redistribute Mosh under the terms of the license -- you may want to consult
>>> your own counsel if uncertain about the GPL's requirements. (Please note
>>> that Mosh is a registered trademark referring to the Mosh software.)
>>>
>>> Best regards,
>>> Keith
>>>
>>> On Wed, Dec 15, 2021 at 7:50 AM Alan Kim <alan at netsarang.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> My name is Alan Kim and I am the Director of Sales & Marketing at
>>>> NetSarang.
>>>> We are developing a new piece of software called PortX. You can see
>>>> more here: https://portx.online/
>>>>
>>>> We'd like to include Mosh into PortX, but want to make sure we go about
>>>> it correctly licensing wise.
>>>> Are we able to incorporate Mosh into our commercial software? If so,
>>>> are we required to purchase a license?
>>>>
>>>> If this is not the right contact for this type of question, can you
>>>> point me in the right direction?
>>>> Look forward to hearing from you. Thank you!
>>>>
>>>> Regards,
>>>>
>>>> *Alan Kim *| NetSarang, Inc. | Director of Sales & Marketing
>>>> 4701 Patrick Henry Dr. BLDG 22 Suite 137, Santa Clara, CA 95054, U.S.A.
>>>>
>>>> Tel: (669) 204-3301 | Email: alan at netsarang.com | Website:
>>>> www.netsarang.com
>>>>
>>>>
>>>> *FACEBOOK: *http://facebook.com/netsarang
>>>> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/facebook-com-netsarang>
>>>>  | *TWITTER**: *http://twitter.com/netsarang
>>>> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/twitter-com-netsarang>
>>>>
>>>> _______________________________________________
>>>> mosh-devel mailing list
>>>> mosh-devel at mit.edu
>>>> https://mailman.mit.edu/mailman/listinfo/mosh-devel
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mit.edu/pipermail/mosh-devel/attachments/20220104/f77cc45b/attachment-0001.htm>