License issue
FelixWeichselgartner opened this issue · 3 comments
Hi,
how can this have MIT-License, when scapy has GPLv2-License?
Greetings
I’m not a lawyer and I certainly don’t want to violate the GPL license of Scapy. If there is any doubt, then I will re-license this script under GPLv2 immediately.
However, as I understand from the GPL FAQ "What if the work is not very long?", it’s okay that we use the MIT license in the case of this script.
Could you elaborate why we have to use GPLv2?
Please also note that we a) do not ship/distribute Scapy and b) did not modify Scapy although that’s probably irrelevant for the license discussion.
I'm not a lawyer either. I was just searching a MIT licensed network scanner, that I can use and ended up finding multiple repositories that use scapy/nmap (both GPL) and licensed their work under MIT (many with more than 300 lines of code).
About the below 300 lines of code rule, I did not know. It might be ok for your case then ("Unless, that is, the code is specially important." - who know what that means...).
Just wanted to point this out, in case this was unwanted.
Thanks for your quick response.
Yes, thanks for pointing this out.
I actually found secdev/scapy#3165 which mentions other libraries that (potentially) violate the GPL.
To clear any doubt, I’ll change the license to GPLv2.