FYI, the GPL license that wget is shipped with is incompatible with the OpenSSL license. Below is a mail message I forward to the development mailing list for lftp and a response from [EMAIL PROTECTED] As far as I know, this only presents a problem when wget binaries linked against OpenSSL are *distributed*. The lftp author has modified the license to allow lftp (distributed under the GPL) to be linked against OpenSSL. [EMAIL PROTECTED] wrote: > > I don't know the specifics but the following is included in the > license for fetchmail 5.8.17 (5.9.0 most recent version): > > Specific permission is granted for this code to be linked to OpenSSL > (this is necessary becuse the OpenSSL license is not GPL-compatible). > > Because lftp is GPL, I presume it is not legal to redistribute > binaries linked against OpenSSL. Any problems adding the above clause > to the lftp license to make it legal? > > BTW, according to: > http://www.fsf.org/licenses/license-list.html#TOCSoftwareLicenses > I believe the incompatibility is the result of the advertising clause > in the OpenSSL license. If you wrote LFTP and do not include or link against code from any other GPL'd source (except fetchmail or others with this permission), there is no problem with adding this to your license. If LFTP includes work from other GPL'd software, then you can't do this. In that case, you might want to consider rewriting OpenSSL using a GPL-compatible license. Or, I hear there's a way to use OpenSSL without linking to it. -- -David "Novalis" Turner, Licensing Question Volunteer, Free Software Foundation -- albert chin ([EMAIL PROTECTED])
