Mercurial Mercurial > repos > enano-1.1 / annotate
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
licenses/tigra-menu.html
author Dan Fuhry <dan@enanocms.org>
Mon, 05 Jul 2010 19:52:10 -0400
changeset 1261 beb0da036222
parent 15 ad5986a53197
permissions -rw-r--r--
DiffieHellman: gracefully handle platforms that fail the sha256 self test, currently only known to be PowerPC. Added support for PHP's built-in hash functions (they were added in 5.1.2) and use them in lieu of the built-in sha256 implementation when available.
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
15
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     1
 
<html>
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     2
 
<head><title>817108</title></head>
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     3
 
<body><h1>Conversation with 817108</h1>
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     4
 
<font color="#204a87"><font size="2">(06:59:52 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> is this the ICQ support for the Softcomplex/Tigra products?</font><br><font color="#204a87"><font size="2">(07:00:42 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> i would like to know about the licensing terms for the Tigra Tree Menu</font><br><font size="2"><font color="#cc0000">(07:01:12 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> sure</font><br><font color="#204a87"><font size="2">(07:01:52 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> according to the license terms, I should be allowed to modify the code, and then distribute it in my own free software, correct?</font><br><font color="#204a87"><font size="2">(07:02:23 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> full credit is given in the source code, as shown in: <a href="http://nighthawk.enanocms.org/includes/clientside/static/admin-menu.js">http://nighthawk.enanocms.org/includes/clientside/static/admin-menu.js</a></font><br><font size="2"><font color="#cc0000">(07:02:23 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> yep</font><br><font color="#204a87"><font size="2">(07:02:41 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> are you familiar with the GNU General Public License at all?</font><br><font size="2"><font color="#cc0000">(07:03:10 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> yep, but I'm not a legal type</font><br><font size="2"><font color="#cc0000">(07:03:35 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> If you prefer GNU, then consider it GNU</font><br><font color="#204a87"><font size="2">(07:04:59 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> wow, thanks =)<br>the problem is that just saying that would probably get me into trouble if someone asked about the license info, because the GPL may in some circumstances go against your licensing terms</font><br><font color="#204a87"><font size="2">(07:05:21 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> the license condition that concerns me is: The above items CAN NOT be modified and then sold as a library component, either individually or together.</font><br><font size="2"><font color="#cc0000">(07:06:07 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> this means that you can't sell it as own modified tree</font><br><font size="2"><font color="#cc0000">(07:06:18 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> if it's the part of larger system then no problem</font><br><font color="#204a87"><font size="2">(07:06:24 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> the GNU General Public License says that you are explicitly allowed to use the code commercially (i.e. charge for it) but you must ensure that any publicly distributed version is also available under the terms of the GPL, and that all recipients are allowed to freely distribute their copies</font><br><font color="#204a87"><font size="2">(07:07:14 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> it also means that someone can take my modified version, modify it further, and then charge for copies of it</font><br><font size="2"><font color="#cc0000">(07:07:17 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> can't be sold deal is just to prevent from creating the competing free or commercial product based on our script</font><br><font color="#204a87"><font size="2">(07:07:49 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> ahh, i see, so that means that i may treat the code as if it were GPL?</font><br><font size="2"><font color="#cc0000">(07:07:55 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> I understand that your product is not competing with the javascript tree</font><br><font color="#204a87"><font size="2">(07:08:28 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> ok, thank you very much for your help, i will update the license block in that file accordingly</font><br><font color="#204a87"><font size="2">(07:14:34 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> just as a side note, you may want to mention that if the free products are used as a part of a larger project that they can be under Free Software licenses, to save yourself from undue annoyances from guys like me ;-)</font><br><font size="2"><font color="#cc0000">(07:15:14 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> luckily very few give a damn about the legal writing ;)</font><br><font color="#204a87"><font size="2">(07:17:45 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> haha<br>is it ok with you if i include an HTML copy of this conversation in the licenses folder in the Enano distribution, as proof of the license conditions?</font><br><font size="2"><font color="#cc0000">(07:18:13 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> ;) that's pretty loose language</font><br><font color="#204a87"><font size="2">(07:18:51 PM) </font><b><font size="3">Dan:</font></b></font><font size="3"></font><font size="3"> well if Enano ever gets in some sort of legal issue, the first thing my lawyer will ask me is, did you document all license info on third party code</font><br><font size="2"><font color="#cc0000">(07:19:31 PM) </font></font><font color="#cc0000"><b><font size="3">817108:</font></b></font><font size="3"></font><font size="3"> ok, then as long a lawyers don't get too much work</font>
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     5
 
</body>
ad5986a53197 Fixed complicated SQL injection vulnerability in URL handler, updated license info for Tigra Tree Menu, and killed one XSS vulnerability
Dan
parents:
diff changeset 
     6
 
</html>
Enano CMS (1.1.x)