Hi Jaak, thanks for the feedback...
On 12/29/18 5:39 PM, Jaak Ristioja wrote:
> Why can't the About= entry contain this information?
The About= entry does contain this information right now, but it usually
contains too much information for a nice, short, description for a UI to
display instructio
I like the idea, because it is useful information for the users. Here
are some of the thoughts I gathered for this:
https://en.wikipedia.org/wiki/Brainstorming";>
Why can't the About= entry contain this information?
I'm unsure whether "UnlockInfo" is the best name.
Is it safe to assume that th
Hi Michael,
There is a new mechanism committed in the latest trunk of SWORD which
allows a publisher to "personalize" an unlock key per user, if they
would like, but SWORD does nothing to try to enforce 'per device' or
'per user' usage.
I have never heard from a publisher that they do not wish to
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 straight
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
<<< text/html; charset=utf-8: Unrecognized >>>
___
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
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 f
