--Boundary-02=_kJWx+buGCHSTarM
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Friday 16 May 2003 16:57, Bernhard Reiter wrote:
> On Thursday 15 May 2003 16:35, Stefan Rompf wrote:
> > Am Donnerstag, 15. Mai 2003 14:34 schrieb Bernhard Reiter:
> > > Just reading the README it is openssl based
> >
> > yes
> >
> > > and links to it.
> >
> > and no. The SSL implementation of KDE loads the openssl libraries
> > on demand - this already happens whenever you access f.e. https
> > URLs. I've just added S/MIME support the KSSL and use it.
> >
> > So the plugin does not introduce new licensing problems.
>
> 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.

As this isn't a KMail specific problem (kssl is in kdelibs/kio) and as=20
kde-licensing has vanished (at least=20
http://mail.kde.org/mailman/listinfo doesn't know anything about this=20
mailing list) I move this discussion to kde-core-devel.

Is there a license problem with OpenSSL or not?

Regards,
Ingo


--Boundary-02=_kJWx+buGCHSTarM
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+xWJkGnR+RTDgudgRAkkfAJ4oQNjJlzTxBgVscgV4liF7eE6JMgCgyYDk
CHceQQm7z0cK+jr9n+BprIc=
=j6/o
-----END PGP SIGNATURE-----

--Boundary-02=_kJWx+buGCHSTarM--