<span style="font-family: Arial;">Sorry for top posting. The engines handle both encryption fine. What may be required from a front-end is reception and deposition of a key<br><br>Sent from my HTC<br><br><div id="htc_header" style="">----- Reply message -----<br>From: "Tonny Kohar" <tonny.kohar@gmail.com><br>To: <chris@burrell.me.uk>, "JSword Developers Mailing List" <jsword-devel@crosswire.org><br>Subject: [jsword-devel] Encrypted modules<br>Date: Mon, Sep 23, 2013 07:55<br><br></div></span><br><div dir="ltr">Hi,<div><br></div><div>As far as I know, the key is added into the particular book conf file, it create an entry there.</div><div><br></div><div>Because it is implemented in that ways, so any fronted which read that conf file should be able to unluck that book, and as far as I know if the front end used jsword lib (not implementing themselves) it is automatically handled by jsword lib/engine</div>
<div><br></div><div>Cheers</div><div>Tonny Kohar</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Sep 22, 2013 at 11:46 PM, Chris Burrell <span dir="ltr"><<a href="mailto:chris@burrell.me.uk" target="_blank">chris@burrell.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi</p>
<p dir="ltr">I have a vague recollection that jsword supports encrypted/locked modules. Where are the keys managed? Does an unlock key unlock all (j)sword frontends?</p><span class="HOEnZb"><font color="#888888">
<p dir="ltr">Chris</p>
</font></span><br>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div><br></div></div>