[jsword-devel] Encrypted modules

[DM Smith]

Also top posting. Briefly from my phone. 

In Book, wrapping Bookmetadata, 2 notions: enciphered and unlocked. The first determines whether it is encrypted. The second only has meaning if encrypted. If so set the key, verify it and save the book metadata. 

In Him
DM 



> On Sep 23, 2013, at 12:26 AM, "refdoc at gmx.net" <refdoc at gmx.net> wrote:
> 
> 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
> 
> Sent from my HTC
> 
> ----- Reply message -----
> From: "Tonny Kohar" <tonny.kohar at gmail.com>
> To: <chris at burrell.me.uk>, "JSword Developers Mailing List" <jsword-devel at crosswire.org>
> Subject: [jsword-devel] Encrypted modules
> Date: Mon, Sep 23, 2013 07:55
> 
> 
> Hi,
> 
> As far as I know, the key is added into the particular book conf file, it create an entry there.
> 
> 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
> 
> Cheers
> Tonny Kohar
> 
> 
>> On Sun, Sep 22, 2013 at 11:46 PM, Chris Burrell <chris at burrell.me.uk> wrote:
>> Hi
>> 
>> 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?
>> 
>> Chris
>> 
>> 
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20130923/a2db50d9/attachment.html>