From kde-core-devel Sat May 17 18:43:57 2003 From: Ingo =?iso-8859-1?q?Kl=F6cker?= Date: Sat, 17 May 2003 18:43:57 +0000 To: kde-core-devel Subject: Re: KSSL based S/MIME plugin available X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105320008211986 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--Boundary-02=_vLox+4r94M+x9SS" --Boundary-02=_vLox+4r94M+x9SS Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Saturday 17 May 2003 20:32, George Staikos wrote: > On Saturday 17 May 2003 12:21, Ingo Kl=F6cker wrote: > > > One could be of the opinion that this puts a legal obligation on > > > applications like e.g. KMail. The question whether KMail is a > > > derived work of OpenSSL is irrelevant in that respect since the > > > license only speaks of "use of this software". I think it's the > > > opinion of the FSF that such additional obligation is > > > incompatible with the GPL. > > > > And also incompatible with the LGPL I assume. Else one could simply > > write an LGPL'd wrapper library and then use this in a GPL program. > > But isn't that exactly what Konqueror does by using kssl? If there > > is no licensing problem between Konqueror and OpenSSL then there > > can't be a problem with KMail (resp. the kssl based S/MIME plugin) > > since both use OpenSSL through kssl. Am I missing something? > > You are correct, KMail is in no different situation than Konqueror. > I'll take care of the IBM issue. I am in the process of contacting > them now. Thanks in advance. I hope everything goes well. Regards, Ingo --Boundary-02=_vLox+4r94M+x9SS Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+xoLvGnR+RTDgudgRAnCIAKCkdbFzmPamw3BKZvb/1GuNBLd3qQCeIBNy YjDxdDrTzeyZNWe86Y6lXZg= =Pwg6 -----END PGP SIGNATURE----- --Boundary-02=_vLox+4r94M+x9SS--