Hello,
On 25.09.2009, at 0:04, João Poupino wrote:
I've attached a small patch that uses your suggestion. I've
successfully tested it with both versions of the Portuguese eID
card, with a SPR532 pinpad reader: one version uses an implicit
change pin operation and the other uses the
Hi Martin,
Understood and thanks for testing the code. I've attached the less
intrusive version of the patch. The card-pteid.c code was changed to
reflect this.
Regards,
João
implicit_pin_change.patch
Description: Binary data
On Sep 25, 2009, at 20:19, Martin Paljak wrote:
Hello,
Hi all,
I've come across an issue with the way a Change PIN operation is
processed in OpenSC, when using a pinpad reader and the Portuguese eID
card. Basically, the problem is that one of the versions of the
Portuguese eID card (IAS spec) only supports changing the PIN if a
previously
Hi,
Don't anything about Portuguese eID but:
...
This works perfectly when using a regular reader. When using a pinpad
reader it works also, but a minor annoyance occurs: the reader asks
for 4 PINs (instead of the regular 3) and I think this can cause
confusion to the users.
If I'm not
Hi François,
Thank you for replying!
On Sep 24, 2009, at 13:36, François Leblanc wrote:
I don't think that the matter is in reader-pcsc.c, I think you should
have a look on Portuguese eID in command pin_cmd the
SC_PIN_CMD_CHANGE
is probably slip in two parts SC_PIN_CMD_VERIFY + the
On the document, there are other options explained. One looks promising:
bConfirmPin: 0x01
bNumberMessage: 0x02
Messages seen on Pinpad display: New Pin*, Confirm Pin*
*In these two cases, old PIN is not asked by the Pinpad but do not forget to
put the old
PIN value in the APDU command.
How
On Sep 24, 2009, at 14:14, François Leblanc wrote:
On the document, there are other options explained. One looks
promising:
bConfirmPin: 0x01
bNumberMessage: 0x02
Messages seen on Pinpad display: New Pin*, Confirm Pin*
*In these two cases, old PIN is not asked by the Pinpad but do
On 24.09.2009, at 15:59, João Poupino wrote:
On the document, there are other options explained. One looks
promising:
bConfirmPin: 0x01
bNumberMessage: 0x02
Messages seen on Pinpad display: New Pin*, Confirm Pin*
*In these two cases, old PIN is not asked by the Pinpad but do not
Thanks for the pointer Martin.
I've attached a small patch that uses your suggestion. I've
successfully tested it with both versions of the Portuguese eID card,
with a SPR532 pinpad reader: one version uses an implicit change pin
operation and the other uses the (normal) explicit pin