Re: apt-https pre-final
On Mon, 3 Jun 2002, Jason Gunthorpe wrote:
>
> On Mon, 3 Jun 2002, Tomas Pospisek wrote:
>
> > > your diff has all sorts of weirdness in the .sgml documents that looks
> > > like a mismatched version or something..
> >
> > Ouh - have you seen that I have patched the sgml stuff as well to document
> > https?
>
> I did, but your diff undoes/redoes/something several unrelated changes to
> the .sgml
I'll fix that.
> > > The openssl license means you can't use pure GPL on the bits you have
> > > applied copyright too..
> >
> > You have to put an "it's OK to link against openssl" into the copyright.
> > That's all. Please see section in my patch that touches the copyright
> > file.
>
> There are a few files you included that have a copyright notice at the top
> that does not include the exception.
I have checked all the licenses. Here's my summary:
file - author, copyright my work - author, copyright
--------------------------------------------------------------------------------------------------
http.cc,h - jgg, none -> https.cc,h - tpo, GPL
connect.h - jgg, none -> connect_ssl.h - tpo, GPL
connect.cc - jgg, none -\
> connect_ssl.cc - tpo, GPL
stunnel.cc - Trojnara, GPL -/
rfc2553emu.cc - jgg, PD
apt-pkg:
crc-16.cc - various, PD
error.cc,h - jgg, PD
fileutl.cc,h - jgg, PD
md5.cc - various, PD
mmap.h - jgg, PD
sha1.cc - various, PD
strutl.cc,h - jgg, PD
system.h - other, PD
all other *.cc,h- jgg, none
These are the files the https is linking against. Most files come without
copyrigh (marked above as "none") and have the last cvs changelog entry
set to you. So I suppose you are their author and the copyright from
COPYRIGHT applies.
The other mentioned files are either PD or in the case of stunnel GPL.
I don't really care about the copyright of my own files. They are mostly
based on yours since I had to build them "compatibly", they are GPL now,
but I can as well put them into the PD, except for connect_ssl.cc which is
based on stunnel.cc so if I want to be fair, I have to put that under GPL
too. Linking stunnel code itself with openssl is of course fine.
So unless you disagree I'm going to add the following note to the bottom
of the COPYING file:
---------------------------------------------------------------------
The https method of apt is linked against openssl. This is herewith
permitted.
The copyright for openssl can be found under /usr/share/doc/openssl/copyright.
The following applies to the https method:
This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit. (http://www.openssl.org/). This product includes
cryptographic software written by Eric Young (eay@cryptsoft.com). This
product includes software written by Tim Hudson (tjh@cryptsoft.com).
---------------------------------------------------------------------
*t
-----------------------------------------------------------------------
Tomas Pospisek
sourcepole - Linux & Open Source Solutions
http://sourcepole.com
Elestastrasse 18, 7310 Bad Ragaz, Switzerland
Tel:+41 (81) 330 77 13, Fax:+41 (81) 330 77 12
------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to deity-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: