|
Lacking a compelling reason to do
otherwise, I have removed spaRV1909 from the eBible.org sword
repository.
I haven't bothered encrypting any Sword modules, yet. I might do that for proprietary copyrighted Bibles in the future if that is what it takes to get permission to distribute them, but I really don't want to get involved in key management and sales. The irony that the guy who contributed encryption algorithm and code to the Sword project currently sees little point in using it has not escaped me. On another topic, one use of cryptography in Bible modules that would be worthwhile would be implementing digital signatures for assurance that a module hasn't been tampered with since it was released. Perhaps another day... On 09/02/2015 09:13 AM, David Haslam wrote: In fact, it was even worse than that. The installed module [spaRV1909] got corrupted due to the fact that the earlier module had not been first removed by Xiphos, as it would have done in the normal course of events.I have just manually removed the eBible module, and reinstalled the CrossWire module [SpaRV1909]. So apart from file date stamps, I'm back to where I was an hour ago. Another possible source of confusion is that the CrossWire module is encrypted, yet comes with its own key. The eBible module [spaRV1909] is not encrypted. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/eBible-org-repository-minor-tweak-tp4655171p4655200.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ 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 --
Aloha,
|
_______________________________________________ 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
