Shridhar Bhat wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > On 24 Nov, Jean-Marc Desperrier wrote:
> >
> > > Shridhar, a tool that incorporates OpenSSL code can hardly be released as
> > > GPL, because OpenSSL itself is not GPL.
> > As I understand the BSD license, BSD licensed code can be rereleased
> > under the GPL. See drivers/scsi/ncr53c8xx.c in the Linux kernel. This
> > code was BSD licensed, it originates from FreeBSD, was ported to Linux
> > and rereleased under the GPL.
Umm. Changing the licence without the consent of the copyright holder is
illegal.
> > > It might be a good idea to take the license of the recent release of
> > > Echohttpd as a model.
> > :-) The license text in echohttpd is stolen from NetBSD, my preferred
> > operating system. So you can say that the license of echohttpd is the
> > BSD license.
> > [looking in to the original 4.4BSD-Alpha source code in the TUHS
> > archive, finding usr/src/etc/COPYRIGHT]
> > Yes. This is _the_ BSD license that was used by the CSRG at Berkley.
>
> I have registered and got the project approved at SourceForge.net.
> While registering the project I chose the License as GPL. Now, after
> recent mails to this thread, I have a question. Can I release my
> code which uses OpenSSL under GPL or not?
Yes.
> And if I can not, then
> is there a way for me to change the license at sourceforge?
> Or, do I need to register my project under a new name and license?
>
> As I understand the OpenSSL license, I can not re-distribute
> *OpenSSL* code under GPL but I don't see any restriction on
> the code which *uses* openssl library.
That's correct.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
