[jsword-devel] Encrypted modules
dmsmith at crosswire.org
Mon Sep 23 18:52:01 MST 2013
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.
> 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
> 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
> Tonny Kohar
>> On Sun, Sep 22, 2013 at 11:46 PM, Chris Burrell <chris at burrell.me.uk> wrote:
>> 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?
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
> jsword-devel mailing list
> jsword-devel at crosswire.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jsword-devel