----Mensaje original----
De: mar...@paljak.pri.ee
Fecha: 24/06/2010 10:27
Para: "Juan Antonio Martinez"<jons...@terra.es>
CC: "Alejandro Vargas"<alejandro....@gmail.com>, 
"opensc-devel@lists.opensc-project.org 
devel"<opensc-devel@lists.opensc-project.org>, "Malcolm 
Bain"<malcolm.b...@id-lawpartners.com>
Asunto: Re: [opensc-devel] Changes on Spanish DNIe licensing

[....]

> > As Direccion General de la Policia has released the code as
> > GPL, we never can integrate it (static compile) into OpenSC.
> > (LGPL can be promoted to GPL. The reverse isn't true). So
> > DNI'e must be built as dynloaded module regardless keys handling
> > 
> > It's a license nightmare: my feeling is that DGP has chosen
> > GPL to ensure that all derived code will be easily auditable

> What about asking them if this is their intent?

We've sent several emails asking for:
- Permission for publishing private keys
- Policy for code approval
- Legal issues on several ways to extract&amp;insert keys into compiled binaries
- Change license from GPL to LGPL or allow dual licensing
- Centralized source code repository (at OpenSC , DGP, or wherever )
- How to handle linux distribution packages

No response (yet)

> There is one thing how they want to release the code
As no response from DGP, we only can elucubrate: on several forums people
talks about a sort of DGP's Source Code Approval Office: developers send
their code to DGP, and if is approved, key bits are added and source code signed
But, it's just an elucubration...

> there's another aspect how it looks from prior infringement aspect (which is 
> pretty obvious now).
Yes: 
- First one: two years of binary code infringing LGPL
- Then two weeks of source code without any license
- Legal status of private keys. As not published under GPL, local law applies:
we cannot publish them, nor publishing scripts to extract. We only can describe 
the
way to obtain... Stupid an incongruent laws...

Im unsure about what OpenSC should do. My feeling is not to include any dnie
bits neither in OpenSC tree nor a separate GPL module subtree until legal 
issues get clear

But in the meanwhile, several repositories have started to work with published 
code. 
I really dislike this situation.

Juan Antonio
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to