Hey,

concerning the license, I think I can speak for (nearly) everyone, if I say:
"We don't really want / need ownership of any contents and never really 
cared about this stuff, as long as it's accurat and if not we'll fix it"
I can only speak for my content (which is the CryptoJPM page), as far as 
this goes it's public domain.
For the license of algorithms and stuff, you'll need an answer by Wei Dai, 
but he never posts here....
As far as cross-compiling and and this kind of stuff goes wait until the 
weekend and I'm pretty sure, Jeffrey Walton will post here and answer your 
question for this part.

Generally, if I'd be you I wouldn't even mind of the license of the 
documentation.
I'm pretty sure you won't harm any author if you just download or read the 
contents and I'm pretty sure that you're allowed to correct things that may 
be wrong.
I'm also pretty sure that you're allowed to use the sample code as public 
domain, although I wouldn't always recommend it as it's not always flawless 
/ ueses weak methods for iluustration (->RandomPool!!!)

That's it from my point, Jeff will clear things up in a few days.

BR

JPM

Am Montag, 9. Februar 2015 16:55:50 UTC+1 schrieb Yaseen Eltii:
>
> What is the Content in The Wiki Under ? as of US Terms of Law Something 
> WIthout a License is the same as ( " look but dont touch" ) your not even 
> allowed to download it 
> "Declaimers" and "About" sections in the wiki are empty so does it fall 
> under the same license as the library ? and who holds the copyright ?
>

-- 
-- 
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.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to