Andreas Jellinghaus wrote:
> true. I'm not a lawyer. on the other hand I have been following
> discussions ..., so I hope I'm totally clueless...
I hope you are rather not so clueless ;-)
--
Regards
Signer: Eddy Nigg, StartCom Ltd.
Phone: +1.213.341.0390
begin:vcard
fn:Eddy Nigg
n:Ni
Ludovic Rousseau wrote:
"License to COPY this document is granted provided that it is
identified as "RSA Security Inc. Public-Key Cryptography Standards
(PKCS)" in all material mentioning or
referencing this document. "
so I can print the document (unchanged, so complient to this license),
and
Ludovic Rousseau wrote:
You have the legal right to _run_ such a combination. The GPL has no
limitation on how you _execute_ the GPL software. You can mix a GPL
code and a proprietary code and use it. What you can't (legally) do is
_distribute_ such a mix.
I thought there was something like tha
Alessandro,
sure, the header file we wrote is a derived work of the pkcs#11 standard
documentation. but that is a book, and what we do is quote certain parts
we need. a book is not a software, there is no license on it, only
copyright. and copyright allows us to quote parts within certain
limit
Martin Paljak wrote:
So if I had an application, 100% GPL and it implemented a 'celan'
pkcs#11 interface that loaded pkcs11-spy (LGPL?) what in turn loads a
StrangeToken$$$ pkcs11 module, that would not be good ?
all code in an application at compile time and runtime must be under GPL
compati
Martin Paljak wrote:
On 28.11.2006, at 0:06, Andreas Jellinghaus wrote:
from a legal point of view I would like opensc being compatible with
the GPL. the rsa header files are not under their current license.
I hope you meant L-GPL.
no,GPL. opensc is and stays under LGPL. but if we have an
I'm trying to diagnose a problem with the PKCS11 interface to the
MuscleCard driver and have found that pkcs15-init cert-loading works
like a charm. However, pkcs11-tool and Mozilla cannot load certificates
onto the card. There is no error raised in the console, but no
certificate appears in the
On Tuesday 28 November 2006 12:04, Christian Horn wrote:
> On Mon, Nov 27, 2006 at 05:35:30PM +0200, Alon Bar-Lev wrote:
> > 1. You don't expect application to require the user to store the
> > PIN hard coded in configuration file...
> > [...]
> > 3. If the user removes and inserts his card, the ap
On Tuesday 28 November 2006 00:29, Andreas Jellinghaus wrote:
> but while we will be able to agree on most parts, I think there
> won't be one solution that fits everyone. for example some people
> are fine with pin in config files, even want that. (if my root
> partition is encrypted, why not stor
On 28.11.2006, at 16:45, Ludovic Rousseau wrote:
The DEBUG symbol is no more used in OpenSC. I then propose to remove
the --enable-debug configure option since it is now useless.
Any objection?
Dead code should be removed.
--
Martin Paljak / [EMAIL PROTECTED]
martin.paljak.pri.ee / ideela
Hello,
The DEBUG symbol is no more used in OpenSC. I then propose to remove
the --enable-debug configure option since it is now useless.
Any objection?
Bye
On 23/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Revision: 3062
Author: nils
Date: 2006-11-23 22:40:01 + (Thu, 23 Nov
On 27/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
Alessandro Premoli wrote:
> The new PKCS#11 header *is* a derivative work of the original RSA
> interface.
you can't put a license on a printed book - the law is quite clear
on that. so if someone reads the book "pkcs#11 (the complete s
On 28/11/06, Martin Paljak <[EMAIL PROTECTED]> wrote:
On 28.11.2006, at 10:56, Werner Koch wrote:
> On Tue, 28 Nov 2006 09:47, [EMAIL PROTECTED] said:
>
>> I hope you meant L-GPL.
>
> An GPLed application can't use an LGPLed library if that library in
> turn uses GPL-incomatible code. Everythi
On Mon, Nov 27, 2006 at 05:35:30PM +0200, Alon Bar-Lev wrote:
> 1. You don't expect application to require the user to store the PIN
> hard coded in configuration file...
> [...]
> 3. If the user removes and inserts his card, the application should
> reprompt for PIN when private object is accesse
On Tue, 28 Nov 2006 10:14, [EMAIL PROTECTED] said:
> Ok, the RSA headers are not GPLed, and then? Who cares? We are not
> going to extend or modify them, we are implementing the official RSA
> PKCS#11 standard after all!
The headers from RSA come with a license that is not compatible to the
GPL:
On Sun, Nov 26, 2006 at 11:19:04PM +0100, Andreas Jellinghaus wrote:
> list
> each software, describe what it does, link to it etc? maybe also
> list which distribution ships what (currently we track that
> in some wikis in the OperatingSystem page).
Would be nice, but keeping track of versions tha
On 28.11.2006, at 10:56, Werner Koch wrote:
On Tue, 28 Nov 2006 09:47, [EMAIL PROTECTED] said:
I hope you meant L-GPL.
An GPLed application can't use an LGPLed library if that library in
turn uses GPL-incomatible code. Everything else would open a
So if I had an application, 100% GPL and i
Werner Koch ha scritto:
I hope you meant L-GPL.
An GPLed application can't use an LGPLed library if that library in
turn uses GPL-incomatible code.
These discussions remind me how wonderful is the BSD license.
--
Alessandro Premoli
smime.p7s
Description: S/MIME Cryptographic Signature
Werner Koch ha scritto:
The new PKCS#11 header *is* a derivative work of the original RSA
interface. If you think implementing RSA PKCS#11 in OpenSC makes it a
No, it is not a derivative work.
You missed the first point of my email and are all focusing on the
second one. Implementing an inte
On 28.11.2006, at 0:29, Andreas Jellinghaus wrote:
with pin in config files, even want that. (if my root partition
is encrypted, why not store sensitive data like that on it?)
With pinpads you start to think differently what a pin is or is not.
It's just impossible to 'store' it then.
times.
On Tue, 28 Nov 2006 09:47, [EMAIL PROTECTED] said:
> I hope you meant L-GPL.
An GPLed application can't use an LGPLed library if that library in
turn uses GPL-incomatible code. Everything else would open a
loophole: Take non-GPL-compatible code, write an LGPLed wrapper and
use that wrapper from
On 28.11.2006, at 0:06, Andreas Jellinghaus wrote:
from a legal point of view I would like opensc being compatible
with the GPL. the rsa header files are not under their current
license.
I hope you meant L-GPL.
--
Martin Paljak / [EMAIL PROTECTED]
martin.paljak.pri.ee / ideelabor.ee
+372
22 matches
Mail list logo
