Skip to content

Add support for ancillary configuration files to unlock modules from STEP Bible #783

Closed
@DavidHaslam

Description

If you have STEP Bible installed on the same machine as Xiphos, then the specially licensed modules distributed by Tyndale STEP could be also opened with Xiphos. However, these modules are generally locked, with the unlock key stored separately from the mods.d folder.

Such an ancillary conf file is stored under the SWORD path in the .\step\jsword-mods.d folder.

The special conf file contents would be:

[modulename]
CipherKey=<theunlockkeyobtainedforthelockedmodule>
STEPLocked=true

Of course, it's feasible to manually open this file, copy the key, and enter it into the Xiphos dialog when prompted, yet it would be neat if this could be done behind the scenes if the unlock key has already come with the module from STEP Bible.

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions