KSSL based S/MIME plugin available

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 17 May 2003 18:08, George Staikos wrote:
> On Saturday 17 May 2003 00:50, Waldo Bastian wrote:
> > > Is there a license problem with OpenSSL or not?
> >
> > OpenSSL comes with advertisement clauses that might cause problems yes:
> > "3. All advertising materials mentioning features or use of this software
> >  *    must display the following acknowledgement:
> >  *    "This product includes cryptographic software written by
> >  *     Eric Young (eay at cryptsoft.com)"
> > and
> >  * 3. All advertising materials mentioning features or use of this
> >  *    software must display the following acknowledgment:
> >  *    "This product includes software developed by the OpenSSL Project
> >  *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
> >
> > 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.
>
>    Yes we've been through this many times before.  It can't be changed,
> everyone (including OpenSSL devels) know it's a problem. 

So what are we going to do about it?

> Given that anything can use KSSL if it uses KIO, where do we stop?  
> I think it's stupid to plaster all of KDE with this.  Once place in
> kdelibs/kdebase is sufficient IMHO.  

 The license demands credit in "All advertising materials". If you think 
that's stupid, then that's because it's a stupid license. Unfortunately we 
are bound by that stupid license as long as we use openssl.

Cheers,
Waldo
- -- 
SCO appears to have the same grasp of reality as the former 
Iraqi information minister (Matt Loney, ZDNet)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+x2oPN4pvrENfboIRAi8VAJ9/xynWHWAdVwyygpFk4kLFGZpzuwCgmrBV
bdX4KlS6sXxrfUGXYBTVWis=
=2vCK
-----END PGP SIGNATURE-----