KSSL based S/MIME plugin available

Ingo Klöcker kloecker at kde.org
Fri May 16 23:12:50 BST 2003

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 
kde-licensing has vanished (at least 
http://mail.kde.org/mailman/listinfo doesn't know anything about this 
mailing list) I move this discussion to kde-core-devel.

Is there a license problem with OpenSSL or not?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030517/c16db336/attachment.sig>

More information about the kde-core-devel mailing list