Hi Daniel,

Am Sonntag 21 August 2011, 23:23:36 schrieb Daniel Kahn Gillmor:
> On 08/21/2011 12:36 PM, Peter Marschall wrote:
> > * renable zlib & readline support
> 
>  [...]
> 
> > what about a new, official Debian package, with my changes as the
> > starting point as starting point?
> 
> i don't think these are compatible with the DFSG, alas.
> 
> GNU readline (at least) is GPL-licensed, and opensc links against
> OpenSSL.  So building a package that links to both of them creates a
> non-redistributable work :(
> 
>  http://people.gnome.org/~markmc/openssl-and-the-gpl.html

I agree with this.
 
> Is there any way to have OpenSC build against some crypto libraries
> other than OpenSSL (preferably licensed in GPL-compatible ways) so we
> could link it to readline without violating one license or the other?

On the other hand: what part of opensc benefits from using readline?
I guess the only place it might be used is the opensc-explorer, and it
works fine for me without readline - so I say lets remove the readline
code to avoid this.

It might be nice to have opensc link with libgcrypt instead of openssl
too. libgcrypt has a very nice interface and is much easier to use than
openssl in my opinion.

but if we work on such a change, we will have some fun with the new stacking:
will applications (that use openssl or libgnutls) still work if that library
or a helper to that lib uses a plugin interface (pkcs#12) to load opensc 
pkcs#12 plugin which is linked to (libcrypto or libgcrypt).

we had problems even with app -> openssl -> opensc -> libcrypto setup in the
past, and I would expect problems here - or this should at least require a lot
of testing to make sure the resulting setup works correctly.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to