-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 12:38 09-01-04, Chris wrote: >On Thu, 8 Jan 2004, Barry Drake wrote: > >> Hi David ........... >> >> On 8 Jan 2004 at 14:16, David's Mailing List and Spam Receiver >> wrote: >> > Basically my idea would be to distribute keys or whatever for >> > OSIS >modules at >> > near cost to me. >> >> I think I'm right in saying that Sword will never directly support >> OSIS >> modules - am I right in this Chris? > >Sword won't directly support un-modified OSIS modules, but it will >(probably pretty soon) support client-side import of OSIS modules. >So, >effectively, this idea should work fine. > >On the other hand, I'm not sure what David has in mind with selling >keys >to XML documents. There might be some work here in figuring out a >good >encrypted XML wrapper, but there are some standard ways of doing this >that >should be considered.
Probably the thing that publishers would buy would be a two-part key: half is the identity of the buyer, and the other half is whatever it takes to transform that identity into the actual key. (Such a thing is easy to write, at least for me, but hard to make secure in open source environments.) This is NOT copy protection, but it is decent point-of-sale control. Alternatively, you could just use ZIP password encryption. It is weak, but then once the XML is sold & unlocked once, the text is in the wild and could be copied freely anyway if someone didn't honor the copyright laws. Michael (Author & inventor of the encryption algorithm you use to lock Sword modules.) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: http://eBible.org/mpj/gpg.htm iD8DBQE//lbRRI/gxxfXR7sRAhJTAJ4rNNfJtH1tRazVoWSinHOg5dxc1QCfeHpQ RzgKAKr3v1GORrJZWFv1mm8= =pKfh -----END PGP SIGNATURE----- _______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel
