Years ago I wrote a proof of concept showing how every customer could
receive a cipher encrypted module with a unique key per user. Nothing stops
any publisher from doing the same if they wanted to avoid having a single
unlock key.
Having it unique to the user's device would be relatively straightforward
to implement in the engine or any front end.
--Greg
On Sat, Dec 29, 2018, 17:08 Michael H <cma...@gmail.com wrote:
> As long as you're opening the unlock option for debate, can I suggest that
> the unlock codes get hashed for the user in some way. That is the user
> provides some kind of credential information to the publisher, which the
> publisher uses some of the info to hash the unlock code, and the resulting
> code will only work on a specific users devices? That would go a LONG way
> to convince hopeful publishers to consider sword platform. This does imply
> that the unlock is only masked 1 level and would still be relatively easily
> unhashed, but it makes the act a deliberate one, and prevents simple eyes
> on the screen theft and impulsive giveaways.
>
> On Sat, Dec 29, 2018 at 4:42 PM ref...@gmx.net <ref...@gmx.net> wrote:
>
>> Sounds good
>>
>> Sent from my mobile. Please forgive shortness, typos and weird
>> autocorrects.
>>
>>
>> -------- Original Message --------
>> Subject: [sword-devel] UnlockInfo .conf entry
>> From: "Troy A. Griffitts"
>> To: SWORD Developers' Collaboration Forum
>> CC:
>>
>>
>> Dear Frontend Developers,
>>
>> In an effort to gain more publishers-- even those who desire to lock and
>> sell some of their modules, I would like to add a new .conf entry:
>>
>> UnlockInfo
>>
>> Up until now, we've relied on the About entry containing something that
>> lets the user know how to obtain unlock codes from publishers selling
>> codes to unlock their modules. This entry would isolate just those
>> instructions to a specific entry and would allow a frontend to do
>> something like:
>>
>> If (moduleToInstall.getConfEntry("UnlockInfo")) {
>>
>> showDialog("
>>
>> The publisher of this modules requires for you to
>> obtain an unlock code. This code can be entered below, instructions
>> from the publisher are as follows:
>> " +
>> moduleToInstall.getConfEntry("UnlockInfo"));
>>
>> }
>>
>> Like many of our entries, this new UnlockInfo entry will allow HTML
>> links and will likely contain a direct link from the publisher to their
>> store entry to purchase an unlock code.
>>
>> An example would be something like:
>>
>> UnlockInfo=An unlock code for the Larry Fitzgerald NFL HOF Edition of
>> the New Testament, with memorable career moments encouraging the
>> believer to press on when those around fall short, may be obtained
>> directly from the NFL store here:
>> href="https://nfl.com/shop/lf-nfl-hof-nt-sword-module";>Larry
>> Fitzgerald
>> NFL HOF Edition of the New Testament - SWORD Module
>>
>> Let me know if you have any comments or ideas,
>>
>> Troy
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
> _______________________________________________
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
