[sword-devel] encryption and integrity checking.
dhowens at pmbx.net
Wed Mar 11 02:17:31 MST 2009
I have thought about this one myself. Surely there is a way that modules
can be flagged as modules not able to be exported using mod2osis or
mod2imp. That is the real issue, if I understand correctly. It should be
a no-brainer that encrypted modules should not be able to be exported.
That requires some mechanism that is secret, but couldn't that mechanism
be built into the way modules are compiled (like a master encryption key
for a module that only the module developer has) which prevents output
of an entire module.
Peter von Kaehne wrote:
> One of the problems which has come up again and again when discussing
> with publishers has been the worry that texts which are released to
> CrossWire become an easy target for abuse - either commercial abuse with
> texts of some commercial importance or, more worrying to me at least -
> manipulation of texts by cults and other entities.
> What possible solutions could we offer to provide text encryption and
> integrity checking in a plausible way which would not violate GPL and
> goes beyond our current practice of simply incorporating a key into the
> conf files?
> This is a serious and important question. I am aware of several texts
> which we did not get or where people hesitate because this is not
> possible right now.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel