Le 10/11/2011 16:46, Frank Morgner a écrit :
> Hi!
>
> BTW, what is the status of SM in trunk. It used to be scheduled for
> 0.12.3. If there is clearity about how to integrate it, I could also
> provide a generic implementation of PACE (generic = "PACE done by OpenSC
> not by the r
Hi!
> >>> BTW, what is the status of SM in trunk. It used to be scheduled for
> >>> 0.12.3. If there is clearity about how to integrate it, I could also
> >>> provide a generic implementation of PACE (generic = "PACE done by OpenSC
> >>> not by the reader").
> >>
> >> There is SM dedicated github
Le 10/11/2011 12:59, Frank Morgner a écrit :
> Hi!
>
>>> BTW, what is the status of SM in trunk. It used to be scheduled for
>>> 0.12.3. If there is clearity about how to integrate it, I could also
>>> provide a generic implementation of PACE (generic = "PACE done by OpenSC
>>> not by the reader").
Hi!
> > BTW, what is the status of SM in trunk. It used to be scheduled for
> > 0.12.3. If there is clearity about how to integrate it, I could also
> > provide a generic implementation of PACE (generic = "PACE done by OpenSC
> > not by the reader").
>
>
> There is SM dedicated github branch
> h
Le 09/11/2011 19:23, Frank Morgner a écrit :
> Hi!
>
>>> Ah yes, I forgot about that. It's already long ago... Anyway, the idea
>>> of sc_transmit_bytes has been given up in favor of sc_bytes2apdu, since
>>> all the opensc tools do not want to send an arbitrary buffer but an
>>> apdu.
>> Will you p
Hi!
> > Ah yes, I forgot about that. It's already long ago... Anyway, the idea
> > of sc_transmit_bytes has been given up in favor of sc_bytes2apdu, since
> > all the opensc tools do not want to send an arbitrary buffer but an
> > apdu.
>
> Will you propose a new patch?
>
> >> Do you need to use
2011/11/9 Frank Morgner :
> Hi!
>
>> > Actually PACE is executed with SCardControl. The current implementation
>> > for control commands in OpenSC would not allow executing PACE, because
>> > reader-pcsc.c:237 always encodes an APDU. This is OK if you are only
>> > using PIN verification/modificati
Hi!
> > Actually PACE is executed with SCardControl. The current implementation
> > for control commands in OpenSC would not allow executing PACE, because
> > reader-pcsc.c:237 always encodes an APDU. This is OK if you are only
> > using PIN verification/modification (which require an encoded APDU
2011/11/8 Frank Morgner :
> Hi!
Hello,
>> > I wrote a patch for libccid to support PACE. Due to a lack of
>> > standardization on the USB level there is only my ccid-emulator, which
>> > can be used with this feature. See
>> > http://sourceforge.net/projects/vsmartcard/ for the libccid patch and
Hi!
> > I wrote a patch for libccid to support PACE. Due to a lack of
> > standardization on the USB level there is only my ccid-emulator, which
> > can be used with this feature. See
> > http://sourceforge.net/projects/vsmartcard/ for the libccid patch and
> > ccid-emulator.
>
> Thanks for the i
Hi!
> > I wrote a patch for libccid to support PACE. Due to a lack of
> > standardization on the USB level there is only my ccid-emulator, which
> > can be used with this feature. See
> > http://sourceforge.net/projects/vsmartcard/ for the libccid patch and
> > ccid-emulator.
>
> Thanks for the i
2011/10/5 Frank Morgner :
> On Wednesday, October 05 at 09:53AM, Ludovic Rousseau wrote:
>>
>> 2011/10/5 Martin Paljak :
>> > On Tue, Oct 4, 2011 at 17:56, Frank Morgner
>> >
>> >> Note that the two readers mentioned above do not use libccid.
>> > Does this mean that they are not CCID compatible?
>
On Wednesday, October 05 at 09:53AM, Ludovic Rousseau wrote:
>
> 2011/10/5 Martin Paljak :
> > On Tue, Oct 4, 2011 at 17:56, Frank Morgner
> >
> >> Note that the two readers mentioned above do not use libccid.
> > Does this mean that they are not CCID compatible?
>
> No. They are CCID compliant A
2011/10/5 Martin Paljak :
> On Tue, Oct 4, 2011 at 17:56, Frank Morgner
>
>> Note that the two readers mentioned above do not use libccid.
> Does this mean that they are not CCID compatible?
No. They are CCID compliant AFAIK (see the notes in [1])
Reiner SCT asked me to remove the support of the
Hello,
On Tue, Oct 4, 2011 at 17:56, Frank Morgner
wrote:
> Hi!
>
>> > You can add Reiner SCT's cyberJack RFID komfort and cyberJack RFID
>> > standard to this list (both also support SM, which is absolutely
>> > transparent to the application). I have been told that filtering VERIFY
>> > (or sim
Hi!
> > You can add Reiner SCT's cyberJack RFID komfort and cyberJack RFID
> > standard to this list (both also support SM, which is absolutely
> > transparent to the application). I have been told that filtering VERIFY
> > (or similar commands) is bound to a certain type of card.
>
> So the fire
2011/10/3 Frank Morgner :
> Hi!
>
>> >> Some pinpad readers have what they call a "firewall". The reader will
>> >> not allow you to use a VERIFY command without using the pinpad feature
>> >> i.e. it is not possible to send a PIN 'in the clear' to the card
>> >> without using the pinpad feature.
>
Hi!
> >> Some pinpad readers have what they call a "firewall". The reader will
> >> not allow you to use a VERIFY command without using the pinpad feature
> >> i.e. it is not possible to send a PIN 'in the clear' to the card
> >> without using the pinpad feature.
> > This should be quite limited l
Le lundi 03 octobre 2011 à 15:07 +0200, Ludovic Rousseau a écrit :
> What models do you have?
> Maybe you have a pinpad reader I do not have myself already.
Thanks Ludovic and Martin. We ordered several PINPAD for testing and we
can't tell more at the moment. We'll get back to you later on.
Kind
2011/10/3 Martin Paljak :
> Hello,
>
> On Mon, Oct 3, 2011 at 16:07, Ludovic Rousseau
> wrote:
>
>> Some pinpad readers have what they call a "firewall". The reader will
>> not allow you to use a VERIFY command without using the pinpad feature
>> i.e. it is not possible to send a PIN 'in the clear
Hello,
On Mon, Oct 3, 2011 at 16:07, Ludovic Rousseau
wrote:
> Some pinpad readers have what they call a "firewall". The reader will
> not allow you to use a VERIFY command without using the pinpad feature
> i.e. it is not possible to send a PIN 'in the clear' to the card
> without using the pin
Hello,
On 10/3/11 3:02 , Jean-Michel Pouré - GOOZE wrote:
> 1) What is OpenSC/libccid current PINPAD support? I have to admit last
> time I used PINPAD was more than a year ago.
What exactly is your question? The support for pinpads has been there
for several years for now. As noted in code, it of
Le 3 octobre 2011 14:02, Jean-Michel Pouré - GOOZE a écrit :
> Dear Friends,
Hello,
> We ordered several PINPAD readers to offer a reliable and affordable
> solution for OpenSC authentication. At first, we are only performing
> testing. We should receive testing readers within the next days. We
Dear Friends,
We ordered several PINPAD readers to offer a reliable and affordable
solution for OpenSC authentication. At first, we are only performing
testing. We should receive testing readers within the next days. We did
not make a choice yet.
So far, our questions are:
1) What is OpenSC/libc
24 matches
Mail list logo
