[tyler.ritchie () gmail com: Fwd: [gaveens () gmail com: Re: About NSE script license field]]

[Benson Kalahar <bensonk () acm wwu edu>]

So, I sent the original query to my friend whose dad is a lawyer.  Here
is their conversation regarding referring to the licenses of other
pieces of software.  

Benson

----- Forwarded message from Tyler <tyler.ritchie () gmail com> -----

Date: Thu, 6 Sep 2007 11:44:32 -0700
From: Tyler <tyler.ritchie () gmail com>
To: Benson Kalahar <bensonk () acm wwu edu>
Subject: Fwd: [gaveens () gmail com: Re: About NSE script license field]

---------- Forwarded message ----------
From: Craig Ritchie <rslaw () olympus net>
Date: Sep 5, 2007 5:26 PM
Subject: RE: [gaveens () gmail com: Re: About NSE script license field]
To: Tyler <tyler.ritchie () gmail com>

 So, I don't think it's a problem just referring to another license and
adopting its terms by reference as long as the other contract is clearly
referenced and easy to find and read.

Dad



-----Original Message-----
*From:* Tyler [mailto:tyler.ritchie () gmail com]
*Sent:* Monday, September 03, 2007 7:20 PM
*To:* Craig Ritchie
*Subject:* Re: [gaveens () gmail com: Re: About NSE script license field]



it's a program, that's why i gave the example with corel and word perfect

-Tyler

On 9/3/07, *Craig Ritchie* < rslaw () olympus net> wrote:

What's "nmap"?

Dad



-----Original Message-----
*From:* Tyler [mailto:tyler.ritchie () gmail com]
*Sent:* Monday, September 03, 2007 1:11 PM
*To:* rslaw () olympus net
*Subject:* Fwd: [gaveens () gmail com: Re: About NSE script license field]



So this would essentially be like having Corel release macros for word
perfect and say "the license is the same as word perfect's" the question
goes to legal legitimacy of a statement like that.

-Tyler

---------- Forwarded message ----------
From: *Benson Kalahar* <bensonk () acm wwu edu>
Date: Sep 3, 2007 12:25 PM
Subject: [gaveens () gmail com: Re: About NSE script license field]
To: despot () gmail com

Can you ask your dad, or shed some light on the legal ramifications of
saying something like "Same as nmap" in the licensing section of a piece
of code's documentation?  It would be nice to have the insight of a
lawyer on this.

Thanks,
Benson

----- Forwarded message from Gaveen Prabhasara < gaveens () gmail com> -----

Subject: Re: About NSE script license field
From: Gaveen Prabhasara <gaveens () gmail com>
To: Nmap Development < nmap-dev () insecure org>
Date: Mon, 03 Sep 2007 23:13:08 +0530

On Mon, 2007-09-03 at 10:59 -0500, Kris Katterjohn wrote:
> Hey everyone!
>
> NSE script license info has been discussed before (
> http://seclists.org/nmap-dev/2006/q3/0156.html), but I am just thinking
> about the existing scripts and how to have consistency in the license
field.
>
Good thing you pointed out the discussion, it brought many ideas
and situations into light. I also think it would be nice to have
a consitant license field among the scripts Nmap officially ships.

> We have things like "See nmaps COPYING for license" and variations of it,
> and then I have "Look at Nmap's COPYING".
>
> I was thinking that, if everyone agrees and it's "legally sound", then we
> can just say "Same as Nmap" instead.  It's simpler and sounds exactly the
> same to me.
Your suggestion seems fine to me, but on the other hand I'm not a
lawyer. In the above mentioned discussion Fyodor stated he was
thinking to do the same licensing as in other code. If it's still
the case, I guess we are free to use something like "Same as Nmap
license. See Nmap's COPYING" or just "Same as Nmap license".

However it's Fyodors call to set licensing terms. It's better to
be on the safe side, especially these days, views and opinions
about Open Source licensing, GPLv2, GPLv3 and BSD license zooming
around.

Cheers,
Gav


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


----- End forwarded message -----

----- End forwarded message -----

Attachment: _bin
Description:

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org