<div><span class="gmail_quote">On 11/03/2009, <b class="gmail_sendername">Peter von Kaehne</b> <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">One of the problems which has come up again and again when discussing<br>with publishers has been the worry that texts which are released to<br>
CrossWire become an easy target for abuse - either commercial abuse with<br>texts of some commercial importance or, more worrying to me at least -<br>manipulation of texts by cults and other entities.</blockquote>
<div>This problem is understandable, but (to my way of thinking) unavoidable.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">What possible solutions could we offer to provide text encryption and<br>integrity checking in a plausible way which would not violate GPL and<br>
goes beyond our current practice of simply incorporating a key into the<br>conf files?</blockquote>
<div>You can't stop it (this is a non-expert view). Anyone can make their own frontend and pull out the text, really. At least some form of cipher protection is provided - unlike some other bible software's module formats...</div>
<div> </div>
<div>Some things that could affect the ease of copying:</div>
<div>We could put the key elsewhere. Then copying the module wouldn't copy the cipherkey.</div>
<div>Not allow use of certain utilities (mod2imp, etc.) on modules with cipherkey set. </div>
<div>Generate a module for each user with a different cipherkey, then you may be able to track where a text came from.</div>
<div> </div>
<div>But these won't keep out a persitent user.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">This is a serious and important question. I am aware of several texts<br>which we did not get or where people hesitate because this is not<br>
possible right now.</blockquote>
<div> </div>
<div>I understand that publishers view this as important, but hiding the encryption procedure is about the only approach I can think of - and not all that good in an opensource library. Maybe we can just point out flaws in other technologies to "reassure" the publishers... ;)</div>
<div> </div>
<div>God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br> in the valley of decision.<br>
<br>Giôên 3:14 (ESV)</div></div>