On 26/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
Hi,
Hello,
the works of smart card software is confusing, so many open source
project. what do you think: shall we start a wiki where we list
each software, describe what it does, link to it etc?
That would be great.
I sometime dis
Hello,
On 25/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
Please have a look at let me know what you think about it. Also if you
spot any difference, typo or problem with the new header file, please
let me know.
I am not sure it is a good idea to change the arguments types.
-/* C_Get
Andreas Jellinghaus ha scritto:
End of August I tried to address the issue on the cryptoki mailing lists
and asked for a license change, but the result was none. However
communicating with other open source projects they understand the
problem and would like to see it solved too.
The problem
On 11/27/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
On 26/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> Hi,
Hello,
> the works of smart card software is confusing, so many open source
> project. what do you think: shall we start a wiki where we list
> each software, describe what
Alon Bar-Lev wrote:
> 3. If the user removes and inserts his card, the application should
> reprompt for PIN when private object is accessed.
>
> 4. If the user removes the card from one reader and insert it to
> another reader, the application should detect that it is the same
> card, and not prom
On 11/27/06, Eddy Nigg (StartCom Ltd.) <[EMAIL PROTECTED]> wrote:
Alon Bar-Lev wrote:
3. If the user removes and inserts his card, the application should
reprompt for PIN when private object is accessed.
4. If the user removes the card from one reader and insert it to
another reader, the
Alessandro Premoli wrote:
> 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
> derivative work and so subjected to RSA's license, then implementing a
> derivative interface doesn't change anything, because of t
Attached is a patch to the the opensc-0.11.1-r3057 snapshot to update
the MuscleCard driver for OpenSC to use an msc_id struct rather than
int/bytes and messing around with byte-swapping for that.
Tested items:
* OpenSC-explorer
* List
* Change Directory
* Read file
* PKCS15:
* Clear
Well...I guess the later is a lot application specificat some
applications you never have to select the certificate anymore, because
it just finds and remembers it and at some you have to do it each
timeNot sure, if this should be a consideration really...
Personally I think, that anything
On 11/27/06, Eddy Nigg (StartCom Ltd.) <[EMAIL PROTECTED]> wrote:
Well...I guess the later is a lot application specificat some
applications you never have to select the certificate anymore, because it
just finds and remembers it and at some you have to do it each timeNot
sure, if this
On 27.11.2006, at 14:24, Ludovic Rousseau wrote:
That would be great.
I sometime discover new smart card applications/programs (like the
pkcs11-helper from Alon Bar-Lev) that could have helped me.
I guess if anyone would have known it before, it would have been
referenced from the wiki as wel
On 27.11.2006, at 16:00, Alessandro Premoli wrote:
It seems completely useless to me. We should use the original and
official RSA headers.
I don't know if the reasoning you gave is legally correct, but from
practical point of view i agree with the original RSA header standpoint.
--
Marti
On Fri, 2006-11-24 at 20:36 +0100, Andreas Jellinghaus wrote:
> Hi,
>
> I re-tested opensc with muscle support today, and if I read the log file
> correctly the situation is this: first a file is created (ok, return
> code 0) and then selected: fails, it does not exist.
>
> https://www.opensc-pr
On 27.11.2006, at 17:35, Alon Bar-Lev wrote:
On 11/27/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
On 26/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> Hi,
Hello,
> the works of smart card software is confusing, so many open source
> project. what do you think: shall we start a w
Oh... It seems like I was not understood correctly...
When I say Application I mean the result behavior for the user.
Whether the application is using a middleware to achieve this or
implement all by it-self is irrelevant to the end-result.
On Monday 27 November 2006 19:38, Martin Paljak wrote:
Alon Bar-Lev wrote:
> Sure it does, it makes users crazy if you re-prompt them for
> certificate that was already selected.
> https://bugzilla.mozilla.org/show_bug.cgi?id=149673
> Opened: 2002-06-06 12:12 (!!)
The Mozilla browser always asks, which certificate to choose
On Monday 27 November 2006 22:12, Eddy Nigg (StartCom Ltd.) wrote:
> Alon Bar-Lev wrote:
> > Sure it does, it makes users crazy if you re-prompt them for
> > certificate that was already selected.
> > https://bugzilla.mozilla.org/show_bug.cgi?id=149673
> > Opened: 2002-06-06 12:12 (
On Mon, 27 Nov 2006 15:00, [EMAIL PROTECTED] said:
> 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. It is an implementation of the
interface defined in the pkcs#11 specs.
Peter Koch wrote:
> Hi all
>
> Daniel Zauft donated a DATEV card (DATEV smartcard classic),
> so I was able to add support for this kind of preformatted TCOS-card.
>
> Please test and let me know whether you were able to use your DATEV
> card or not.
>
>
Hi,
i finally managed to compile the pa
On 27.11.2006, at 22:24, Alon Bar-Lev wrote:
While in my webmail site, I need to select a certificate almost very
time I select an item... This is bad... Even I cannot work with it.
Check your webserver coniguration and SSL session timeout. Mozilla
only asks for a certificate when the SSL
On 11/27/06, Martin Paljak <[EMAIL PROTECTED]> wrote:
In theory, all software that can in some way make use of asymmetric
crypto, can use smartcards. We might 'see the problem', document a
better and brighter future, enlighten developers and offer ready
solutions to some of the problem that plagu
Alon Bar-Lev wrote:
>> The Mozilla browser always asks, which certificate to choose when
>> performing client authentication. I don't see anything wrong with
>> that...With Thunderbird, when a certificate has been correctly
>> associated with the account, there is no need to re-select. In both
>> c
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 standard,
not the header files)", and notes down the definitions
Martin Paljak wrote:
from practical point of view i agree with the original RSA header standpoint.
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.
Regards, Andreas
Alon Bar-Lev wrote:
But before we do, I think we need to define what is smartcard support...
There are quality criteria that should be listed for each application,
describing its level of support.
this whole section should be put into a style guide for adding
smart card support I think.
but wh
Ludovic Rousseau wrote:
I am not sure it is a good idea to change the arguments types.
that is not intentional, any difference is a bug and needs
to be fixed.
Should'nt we stick to the API as defined in the standard?
yes. but replacing the header files with something GPL compatible
would be
On Mon, Nov 27, 2006 at 09:26:14PM +0100, Daniel Zauft wrote:
> I don't have any idea of the purpose of this certificate or the
Perhaps it's similar to the extra cert on NIDEL, the newest Swedish
ID card.
The idea is that applications can check that this is in fact a real
national ID card and not
Daniel Zauft <[EMAIL PROTECTED]> schrieb:[...]
It's quite interesting that opensc reveals a hidden certificate, not
shown by the Sicherheitspaket ("DATEV Signatur Zertifikat"), which is
issued by an unknown (maybe just non-public) CA ("CA DATEV AUTH 2:PN").
I don't have any idea of the purpose o
28 matches
Mail list logo
