<div dir="auto">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.<div dir="auto"><br></div><div dir="auto">Having it unique to the user's device would be relatively straightforward to implement in the engine or any front end.</div><div dir="auto"><br></div><div dir="auto">--Greg</div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 29, 2018, 17:08 Michael H <<a href="mailto:cmahte@gmail.com">cmahte@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">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. </div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 29, 2018 at 4:42 PM <a href="mailto:refdoc@gmx.net" target="_blank" rel="noreferrer">refdoc@gmx.net</a> <<a href="mailto:refdoc@gmx.net" target="_blank" rel="noreferrer">refdoc@gmx.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sounds good<br><br>Sent from my mobile. Please forgive shortness, typos and weird autocorrects.<div class="m_8109161977261073000gmail-m_-3559698534208794442quote" style="line-height:1.5"><br><br>-------- Original Message --------<br>Subject: [sword-devel] UnlockInfo .conf entry<br>From: "Troy A. Griffitts" <u></u><br>To: SWORD Developers' Collaboration Forum <u></u><br>CC: <br><br><br type="attribution"><blockquote class="m_8109161977261073000gmail-m_-3559698534208794442quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Frontend Developers,<br><br>In an effort to gain more publishers-- even those who desire to lock and<br>sell some of their modules, I would like to add a new .conf entry:<br><br>UnlockInfo<br><br>Up until now, we've relied on the About entry containing something that<br>lets the user know how to obtain unlock codes from publishers selling<br>codes to unlock their modules. This entry would isolate just those<br>instructions to a specific entry and would allow a frontend to do<br>something like:<br><br>If (moduleToInstall.getConfEntry("UnlockInfo")) {<br><br> showDialog("<p>The publisher of this modules requires for you to<br>obtain an unlock code. This code can be entered below, instructions<br>from the publisher are as follows:</p>" +<br>moduleToInstall.getConfEntry("UnlockInfo"));<br><br>}<br><br>Like many of our entries, this new UnlockInfo entry will allow HTML<br>links and will likely contain a direct link from the publisher to their<br>store entry to purchase an unlock code.<br><br>An example would be something like:<br><br>UnlockInfo=An unlock code for the Larry Fitzgerald NFL HOF Edition of<br>the New Testament, with memorable career moments encouraging the<br>believer to press on when those around fall short, may be obtained<br>directly from the NFL store here: <a rel="noreferrer">href="https://nfl.com/shop/lf-nfl-hof-nt-sword-module">Larry Fitzgerald<br>NFL HOF Edition of the New Testament - SWORD Module</a><br><br>Let me know if you have any comments or ideas,<br><br>Troy<br><br><br><br>_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank" rel="noreferrer">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</blockquote></div>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>