My suggestion would be to add few simple statements that give clear hypothetical examples of what is allowed or not allowed.
For example, if I write a program and use Serpent and RSA code from Crypto++, what part of the distinction does it fall under? If I am allowed, perhaps a point would be: - You may use parts or all of Crypto++ in your program, without worrying about the license. And then... following that, give a scenario as to what the other side of the <distinction> is. Perhaps it's something along the lines of: You cannot bundle package Crypto++ in full to release it as your own work. ... but then it gets confusing. "A distinction is made between the library as a compilation (i.e., collection), which is copyrighted by Wei Dai, and the individual files in it, which are public domain. " So if I take all the individual files in it, except for 1 file of my choosing, does that mean it is no longer a collection, since it's not the full Crypto++? What then? What restrictions do I have on that? In my first scenario I used only 2 .cpp files (and the other stuff it needs to get those two .cpp files to work), so that might fall under using two "individual files". But what if I was Mr. Bigshot and included the entire Crypto++ in my app, and used every single feature? Would I then not be using the individual files, but "the library as a compilation (i.e., collection)" ? I don't know. On Tue, Nov 30, 2010 at 5:38 PM, Wei Dai <[email protected]> wrote: I thought my explanation on the website was pretty clear, but apparently > not. Can anyone suggest any changes to the text that might make it clearer? > > -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
