It's not particularly more well-known than any type of open standard would be. For instance, the mythological hacker who's trying to use the module for free will not know what the exact contents of the OSIS/GBF/ThML might have been, so they would really be knowing more than that. In this case they have the data (scripture text) and not the mark-up. For someone trying to figure out encrypted communications they will usually know the structure but not the data. We're just in the flip position.
<br><br><div><span class="gmail_quote">On 3/2/06, <b class="gmail_sendername">L.Allan-pbio</b> <<a href="mailto:paraclete@bibleinverse.org">paraclete@bibleinverse.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
IANASE either.<br><br>Something to consider (in addtion to something like a CRC or MD5 hash) ....<br>perhaps the .conf file could have a known pattern for the first several<br>characters and last several characters. For example, the KJV begins with:
<br>"In the" and finishes with "Amen."<br><br>It something else shows up, something is amiss. Having the last expected<br>letters also gives something of a "sanity check" on whether versification is
<br>ok.<br><br>I suppose providing the known letters is "leaking" some encryption info, but<br>it doesn't take much detective work to find out what the contents are. :-p<br><br>BTW, it is something of an anomaly compared to most encryption situations
<br>... the contents are completely known ... I suppose CrossWire's obligation<br>to the publisher is to make it difficult to utilize without paying the<br>license fee.<br><br>_______________________________________________
<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel
</a><br>Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br>