In message <[EMAIL PROTECTED]> on Tue, 26 Jul 2005 08:59:01 -0400, Charles Gagnon <[EMAIL PROTECTED]> said:
charlesg> I help maintain wput, a command-line ftp-client that looks charlesg> like wget but instead of downloading, uploads files or whole charlesg> directories to remote ftp-servers (http://wput.sourceforge.net/). charlesg> charlesg> Our latest release candidate uses OpenSSL. Before we release charlesg> it, we want to make sure we are following whatever charlesg> legalities OpenSSL requires. Currently, the wput code under charlesg> GPL and ships with a copy of "GNU GENERAL PUBLIC LICENSE", charlesg> Version 2, June 1991. charlesg> charlesg> If anything else should be requested or included with the charlesg> source to make us square with OpenSSL, please let me know. >From an OpenSSL point of view, there is no problem. However, the GNU project defines OpenSSL as incompatible with the GPL, as you can see on http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses (you need to scroll down a little bit). I believe the solution that has been offered so far is to add a note below the copyright statement in each file, saying it is allowed to link your source with OpenSSL. You might want to ask RMS or anyone else in the GNU community, but be prepared that they will try to push you to use GNUtls instead. Whether you do so or not is, of course, your choice. Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
