The RSAREF 2.0 license states that you have the right:
"to copy and distribute the Program and Application Programs
in accordance with the limitations set forth in Section 2."
where the terms in section 2 include:
"a. RSA owns the Program and its associated documentation and
all copyrights therein. You may only use, copy, modify and
distribute the Program as expressly provided for in this
Agreement. You must reproduce and include this Agreement,
RSA's copyright notices and disclaimer of warranty on any
copy and its associated documentation. The Program and any
Application programs must be distributed with their source code.
b. The Program may not be used directly for revenue-generating
purposes. You may not:
<snip>
(ii) license or otherwise distribute any Application Program
in any manner that generates income to you, including
without limitation any income on account of license
fees, royalties, maintenance fees and upgrade fees; and
(iii) license or otherwise distribute any Application
Program without the express written acknowledgment of
the end user that the Program will not be used in
connection with any revenue-generating activity of the
end user.
<snip>
c. The Program, if modified, must carry prominent notices
stating that changes have been made, and the dates of any
such changes.
d. Prior permission from RSA in writing is required for any
modifications that access the Program through ways other
than the published Program interface or for modifications
to the Program interface. RSA will grant all reasonable
requests for permission to make such modifications."
My reading of this is that you can distribute RSAREF as long as you include
the sources, all of the original legal documentation & license info, clearly
document any modifications, DON'T SEE ANY REVENUE, and have express written
permission from RSADSI for any changes that you make to the API.
*I'm not a lawyer*, but it seems like everything you describe is permissible
under the license, provided you document all of your changes, provide the
source and all of the original license info.
Dave Neuer
-----Original Message-----
From: Erik Kline <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, April 13, 1999 6:19 PM
Subject: Re: RSARef No Longer Available (Was RSAref in the US)
>
>
>> can still download and use it if you can find it elsewhere and that you
can
>> even post it for download as long as it's in the same form in which you
>> received it.
>
>Well, many of us have the rsaref20.tar.Z tarball from ftp.rsa.com, I'm
>sure. Is it really going to be legal for one of us to post it somewhere?
>Also, I went so far as to build an RPM that makes librsaref.a and
>librsaref.so for linux-x86. It sounds like that might be inviting disaster
>to post that SRPM, but I'd still kind of like to do so. I could just post
>the patch and the spec file I suppose... What's the word on all this?
>
>__________
>Erik Kline
>ekline.com
>
>______________________________________________________________________
>OpenSSL Project http://www.openssl.org
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
