MJ Ray <[EMAIL PROTECTED]> wrote: > I thought the API reference was the PDF from > http://www.rsasecurity.com/rsalabs/pkcs/pkcs-11/ > which has a slightly different licence and wouldn't be copied > wholesale anyway, just the few names for interfacing.
I also checked the licence of the PDF file and it _also_ contains a publicity clause. Page 289 I find: " D Intellectual property considerations [...] License to copy this document is granted provided that it is identified as "RSA Security Inc. Public-Key Cryptography Standards (PKCS)" in all material mentioning or referencing this document. " I just noted that the RSA header licence contains: "in all material mentioning or referencing this software." but the PDF licence contains "in all material mentioning or referencing this document.". Note the difference: "cryptoki software" in the header file and "PKCS document" in the PDF. The mozilla licence contains the version with "PKCS document". I don't know where it comes from. I don't think it make it more GPL compatible. > It is interesting. Could one read the API reference documentation > and recreate the header files from the ideas? That would be a real challenge. The API defines A LOT of constants. It seams the only human possible solution is to ask RSA to change their licence. I guess the Mozilla foundation could help if they care about licencing issues. Any idea of how we should contact Mozilla and RSA? I am really _not_ a diplomatic guy :-) Thanks, -- Ludovic Rousseau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
