Full Disclosure mailing list archives

Re: INSECT Pro - Free tool for pentest - New version release 2.7


From: GloW - XD <doomxd () gmail com>
Date: Wed, 31 Aug 2011 14:24:54 +1000

So basically once you sign over a GPL v2 , you sign over any right to misuse
even the code wich you have written ?
i guess i thought this could be scrutinized outside of the GPL via means of
a solicitor but, if the law is complacent about use and misse then, i guess
thats that and your correct, i have actually yes, used myself the CC lisence
and was thinking the gpl was just a simpler version but seems that is
probably safer to go wityh CC i guess there atleast you have some say over
mis-use in cases where you specify wich docunments in particular, ie:
sourcecode1.cpp,source2.cpp and v.cpp must not be modified... the rest could
be.., for example.
Ohwell, that shoots any theory then of why it is even being mentioned in the
list, other than to potentially harm all users of tightvnc src.
Stranger things have happened i guess.. Sorry for my earlier report and,
enjoy the code!
lol
xd
cheers Valdis ..




On 31 August 2011 14:14, <Valdis.Kletnieks () vt edu> wrote:

On Wed, 31 Aug 2011 13:36:12 +1000, GloW - XD said:

So, i think this should clear up alittle of this small debacle wich has
broken about GPL... GPL is usually there to protect the src code in the
GPL
(named), but is also, not to be used in ways wich defame, wich is why it
exists.. if tightvnc wanted to now, they could look at ALL its uses and
scrutinize them in every case, and why the code is being used. It is
something wich is verymuch now up to them and up to wether people have
modified theyre code.

Ahem.  What the GPL V2 actually says:

 6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

"Not to defame" is an additional restriction, as is " scrutinize why the
code
is being used". You can't do either of those for a GPL-licensed package -
you
may be thinking of some of the Creative Commons licenses.


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Current thread: