From kde-core-devel  Sun May 18 10:52:34 2003
From: Matthias Welwarsky <matze () stud ! fbi ! fh-darmstadt ! de>
Date: Sun, 18 May 2003 10:52:34 +0000
To: kde-core-devel
Subject: Re: KSSL based S/MIME plugin available
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105325553504003
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_1X2x+SXT07CUZ73"


--Boundary-02=_1X2x+SXT07CUZ73
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Saturday 17 May 2003 00:12, Ingo Kl=F6cker wrote:
> On Friday 16 May 2003 16:57, Bernhard Reiter wrote:
> > AFAIK dynamic linking would be considered a derived work in this
> > situation, even when done on demand.
> > Thus is would still be a bit problematic. Compare:
> >
> > http://www.fsf.org/licenses/gpl-faq.html#GPLAndPlugins
> > 	If the program dynamically links plug-ins,
> > 	and they make function calls to each other
> > 	and share data structures, we believe they form a single program,
> > 	so plug-ins must be treated as extensions to the main program.
> > 	This means they must be released under the GPL
> > 	or a GPL-compatible free software license,
> > 	 and that the terms of the GPL must be followed
> > 	when those plug-ins are distributed.

Well, so if OpenSSL does not make calls into the KDE code and does not acce=
ss=20
private KDE data structures, this does not apply. If the OpenSSL API is=20
callback driven, we're lost, though.

regards,
	matze

=2D-=20
Matthias Welwarsky
=46achschaft Informatik FH Darmstadt
Email: matze@stud.fbi.fh-darmstadt.de

"all software sucks equally, but some software is more equal"

--Boundary-02=_1X2x+SXT07CUZ73
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+x2X1ANO+fpRuZ2IRAp4zAJ48oWJ4e1bZ88dWdCyJmeMCQa0myACfWwW/
7ZHaIhcnsDOSkVPJR1cWenM=
=EDJg
-----END PGP SIGNATURE-----

--Boundary-02=_1X2x+SXT07CUZ73--