Mailing List Archive: GnuPG: devel

scd-backport-2-0 branch

Index | Next | Previous | View Threaded

gniibe at fsij

Jun 21, 2012, 7:49 PM

Post #1 of 10 (217 views)
Permalink

scd-backport-2-0 branch

Hello,

I backported SCD (scdaemon) related changes to scd-backport-2-0
branch. If it doesn't have any problem, I'd like to merge it into
STABLE-BRANCH-2-0.

Here are changes incorporated into scd-backport-2-0.

commit a90f0fca554a679e1c09b0c11ed80311a9358a9d
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Jun 22 10:51:12 2012 +0900

scd: Fix updating slot status.
* scd/comman.c (do_reset): Let clear card_removed flag.

commit ff40c05e8b563471278cb7c92df0310bc5967749
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Mon Jun 18 15:08:01 2012 +0900

scd: acquire lock in new_reader_slot.

* scd/apdu.c (new_reader_slot): Acquire lock.
(open_ct_reader, open_pcsc_reader_direct, open_pcsc_reader_wrapped)
(open_ccid_reader, open_rapdu_reader): Release lock.

--
Fixes a test case of:
No libpcsclite1 installed.
Run gpg-agent
Run command "gpg-connect-agent learn /bye" with no card/token
Sometimes it fails: ERR 100663356 Not supported <SCD>
While it should be always: ERR 100663404 Card error <SCD>

commit 7f3ea446609355c96e90f0b6beb057daa1152643
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Mon Jun 18 14:52:53 2012 +0900

scd: move lock_slot, trylock_slot, unlock_slot functions.

* scd/apdu.c (lock_slot, trylock_slot, unlock_slot): Move.

--
This is for upcoming changes.

commit 29b431fcf97a9e615d34a7a40e570e63834b360a
Merge: 3e39a9a cc13771
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Jun 15 16:50:45 2012 +0900

Merge branch 'scd-backport-2-0' of git+ssh://playfair.gnupg.org/git/gnupg into scd-backport-2-0

commit 3e39a9aeaadd9d4ea7ea578dc77504bd1fd6e30a
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Jun 15 16:46:59 2012 +0900

scd: Fix merge mistake.
* scd/iso7816.c (iso7816_reset_retry_counter): Implement.

commit d138fe5c30c877856b4c397147bb0090705821f8
Author: Werner Koch <wk [at] gnupg>
Date: Thu Dec 15 21:45:35 2011 +0100

scd: Prefer application Geldkarte over DINSIG.

* scd/app.c (select_application): Reorder application tests.
--

Although the DINSIG application is available on most German cards, it
is in reality not used. Thus showing the Geldkarte application is
more desirable for a good user experience.

commit 2586eac997911869008cb3ba57865a7d63a2afc3
Author: Werner Koch <wk [at] gnupg>
Date: Mon Dec 19 18:26:47 2011 +0100

scd: Fix for card change returning GPG_ERR_CARD_RESET.

* scd/apdu.c (apdu_connect): Do not test for zero atrlen.
--
When gpg-agent prompts for insertion of a card this error would be
returned.

Co-authored-by: Ben Kibbey <bjk [at] luxsci>

commit 685955444823a5ca1190b109043ee773bf206bae
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Jan 6 13:50:21 2012 +0900

Merge ccid_driver_improvement branch. (backport)

* scd/apdu.c (ccid_keypad_operation): Rename from ccid_keypad_verify.
(open_ccid_reader): Use ccid_keypad_operation for verify and modify.

* scd/ccid-driver.c (VENDOR_VASCO, VASCO_920): New.
(ccid_transceive_apdu_level): Permit sending packet where
apdulen <= 289. Support receiving packets in a chain.
(ccid_transceive_secure): Maximum is 15 for VASCO DIGIPASS 920.
Support keypad_modify method such as CHANGE_REFERENCE_DATA: 0x24.

commit f78cdf6d45708b67bc3d7bf7b90283254fdd23fd
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Tue Dec 20 13:34:27 2011 +0900

Add error log and debug log for pcsc_keypad_verify and pcsc_keypad_modify.

* scd/apdu.c (pcsc_keypad_verify): Add debug log and error log.
(pcsc_keypad_modify): Likewise.

commit 1b0968ce9a642671f902ceddbafb5af4fe51535b
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Dec 2 13:57:12 2011 +0900

Fix pinpad input support for passphrase modification. (backport)

* apdu.c (pcsc_keypad_verify): Have dummy Lc field with value 0.
(pcsc_keypad_modify): Likewise.
(pcsc_keypad_modify): It's only for ISO7816_CHANGE_REFERENCE_DATA.
bConfirmPIN value is determined by the parameter p0.

* app-openpgp.c (do_change_pin): The flag use_keypad should be 0 when
reset_mode is on, or resetcode is on. use_keypad only makes sense for
iso7816_change_reference_data_kp.

* iso7816.h (iso7816_put_data_kp): Remove.
(iso7816_reset_retry_counter_kp): Remove.
(iso7816_reset_retry_counter_with_rc_kp): Remove.
(iso7816_change_reference_data_kp): Add an argument: IS_EXCHANGE.

* iso7816.c (iso7816_put_data_kp): Remove.
(iso7816_reset_retry_counter_kp): Remove.
(iso7816_reset_retry_counter_with_rc_kp): Remove.
(iso7816_change_reference_data_kp): Add an argument: IS_EXCHANGE.

commit b480f18e1de71766fc6b4fb3c50e157d0abffda5
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Thu Dec 1 11:09:51 2011 +0900

scd: Fix pinpad input support (backport from master)

* app-openpgp.c (do_change_pin): Fix pincb messages when
use_keypad == 1.

commit 7cd8b12e25b6daabedf6fdc2f350327e2116fc78
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Tue Nov 29 11:59:32 2011 +0900

scd: PC/SC pinpad support (pinpad input for modify pass phrase). (backport)

* iso7816.h (iso7816_change_reference_data_kp): Remove arguments
of OLDCHV, OLDCHVLEN, NEWCHV, and NEWCHVLEN.

* iso7816.c (iso7816_change_reference_data_kp): Call
apdu_keypad_modify.
(iso7816_change_reference_data): Don't call
iso7816_change_reference_data_kp.

* apdu.h (apdu_keypad_modify): New.

* apdu.c (pcsc_keypad_modify, apdu_keypad_modify): New.
(struct reader_table_s): New memeber function keypad_modify.
(new_reader_slot, open_ct_reader, open_ccid_reader)
(open_rapdu_reader): Initialize keypad_modify.

* app-openpgp.c (do_change_pin): Handle keypad and call
iso7816_change_reference_data_kp if it is the case.

commit 6dc187f2dbf3b5e7322fa40c7e085da12ad373d2
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Mon Nov 28 16:16:38 2011 +0900

scd: PC/SC pinpad support. (Backported from master.)

* iso7816.h (iso7816_verify_kp): Remove arguments of CHV and CHVLEN.

* iso7816.c (iso7816_verify_kp): Call apdu_keypad_verify. Only
handle thecase with PININFO.
(iso7816_verify): Call apdu_send_simple.

* app-openpgp.c (verify_a_chv, verify_chv3): Follow the change of
iso7816_verify_kp.

* app-nks.c (verify_pin): Likewise.

* app-dinsig.c (verify_pin): Likewise.

* apdu.c: Include "iso7816.h".
(struct reader_table_s): New memeber function keypad_verify.
Add fields verify_ioctl and modify_ioctl in pcsc.
(CM_IOCTL_GET_FEATURE_REQUEST, FEATURE_VERIFY_PIN_DIRECT)
(FEATURE_MODIFY_PIN_DIRECT): New.
(pcsc_control): New.
(control_pcsc_direct, control_pcsc_wrapped, control_pcsc)
(check_pcsc_keypad, pcsc_keypad_verify): New.
(ccid_keypad_verify, apdu_keypad_verify): New.
(new_reader_slot): Initialize with check_pcsc_keypad,
pcsc_keypad_verify, verify_ioctl and modify_ioctl.
(open_ct_reader): Initialize keypad_verify with NULL.
(open_ccid_reader): Initialize keypad_verify.
(open_rapdu_reader): Initialize keypad_verify with NULL.
(apdu_open_reader): Initialize pcsc_control.

* pcsc-wrapper.c (load_pcsc_driver): Initialize pcsc_control.
(handle_control): New.
(main): Handle the case 6 of handle_control.

commit cc13771675f83624a7d850b73f92e43e085b71c8
Author: Werner Koch <wk [at] gnupg>
Date: Wed Jun 13 09:35:41 2012 +0200

Fix generated ChangeLog entry.

--
Finally Jim's git-fix-log thingy comes handy.

commit a3ae21162ae14a6a1661ef1a6937601f6914528b
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Tue Jun 12 14:51:52 2012 +0900

scd fixes on error.

* scd/apdu.c (open_pcsc_reader_wrapped): Show error number.

* scd/command.c (get_reader_slot): Return -1 on error.

commit 31584d3659497c0fff26f129c8c16a57a9e2330b
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Fri Jun 8 13:18:06 2012 +0900

scd: Fix the changes of scd/command.c

* scd/command.c (do_reset): Assign slot after setting slot_table.

commit ffd7ebf62963adb044ee56f0e1b87be837b8f179
Author: Werner Koch <wk [at] gnupg>
Date: Wed Dec 14 10:30:01 2011 +0100

scd: Fix resetting and closing of the reader. (Backported by gniibe)

* scd/command.c (update_card_removed): Do no act on an invalid VRDR.
(do_reset): Ignore apdu_reset error codes for no and inactive card.
Close the reader before setting the slot to -1.
(update_reader_status_file): Notify the application before closing the
reader.
--

With this change the scd now works as it did in the past. In
particular there is no more endless loop trying to open the reader by
the update_reader_status_file ticker function. That bug basically
blocked all card operations until the scdaemon was killed.

commit fae87058eac21b41e6ec0ad6dca1f4b4f806ab73
Author: Werner Koch <wk [at] gnupg>
Date: Mon Dec 12 21:02:54 2011 +0100

scd: Retry command SERIALNO for an inactive card.

* scd/command.c (cmd_serialno): Retry once for an inactive card.

commit 775a5f4b92fde3151d0faa88fae2b8ccfbea2928
Author: Werner Koch <wk [at] gnupg>
Date: Mon Dec 12 20:34:12 2011 +0100

Fix detection of card removal and insertion.

* scd/apdu.c (apdu_connect): Return status codes for no card available
and inactive card.
* scd/command.c (TEST_CARD_REMOVAL): Also test for GPG_ERR_CARD_RESET.
(open_card): Map apdu_connect status to GPG_ERR_CARD_RESET.

commit 08178d1e130a856622c0b938a34eb109bde79262
Author: Werner Koch <wk [at] gnupg>
Date: Fri Dec 2 18:09:58 2011 +0100

Support the Cherry ST-2000 card reader.

* scd/ccid-driver.c (SCM_SCR331, SCM_SCR331DI, SCM_SCR335)
(SCM_SCR3320, SCM_SPR532, CHERRY_ST2000): New constants.
(parse_ccid_descriptor): Use them.
(scan_or_find_usb_device, ccid_transceive_secure): Handle Cherry
ST-2000. Suggested by Matthias-Christian Ott.

commit dafa7aa621dfe36c5c6cf462d3ec0d6c614ab105
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Thu Jan 13 16:38:31 2011 +0900

fix wLangId in ccid-driver.c
--

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

gniibe at fsij

Jun 21, 2012, 8:19 PM

Post #2 of 10 (207 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On 2012-06-22 at 11:49 +0900, NIIBE Yutaka wrote:
> I backported SCD (scdaemon) related changes to scd-backport-2-0
> branch. If it doesn't have any problem, I'd like to merge it into
> STABLE-BRANCH-2-0.

BTW, during the work of backport, I couldn't understand the reason why
scdaemon remains after removal of card (or removal of card reader /
token). I think that it is easier to just shutdown scdaemon when
it detects removal of card.

Please teach me about the design of scdaemon.
--

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Jun 22, 2012, 1:25 AM

Post #3 of 10 (206 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On Fri, 22 Jun 2012 04:49, gniibe [at] fsij said:

> I backported SCD (scdaemon) related changes to scd-backport-2-0
> branch. If it doesn't have any problem, I'd like to merge it into
> STABLE-BRANCH-2-0.

I am fine with this. Shall I prepare a release candidate then?

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Jun 22, 2012, 1:32 AM

Post #4 of 10 (206 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On Fri, 22 Jun 2012 05:19, gniibe [at] fsij said:

> BTW, during the work of backport, I couldn't understand the reason why
> scdaemon remains after removal of card (or removal of card reader /
> token). I think that it is easier to just shutdown scdaemon when
> it detects removal of card.

One reason is that scdaemon monitors the card reader and tells other
application about the presence of a card. The main mechanism for this
are the "reader_N.status" files. There is also an option to run a script
and meanwhile I may even agree to add d-bus support as an option.

Another reason is that we eventually want to support RFID reader where
the card presence is not as easy monitored as with USB tokens or card
readers.

What we should change is the baroque way of setting up channels between
gpg-agent and scdaemon; i.e. a mix of pipe and socket servers. To
streamline the system it would be better to use a well known socket for
scdaemon in the same way as gpg-agent does it. But that is something
for 2.1.

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wking at tremily

Jun 22, 2012, 2:10 AM

Post #5 of 10 (205 views)
Permalink

Re: [GnuPG] Re: scd-backport-2-0 branch [In reply to]

On Fri, Jun 22, 2012 at 10:32:36AM +0200, Werner Koch wrote:
> What we should change is the baroque way of setting up channels between
> gpg-agent and scdaemon; i.e. a mix of pipe and socket servers. To
> streamline the system it would be better to use a well known socket for
> scdaemon in the same way as gpg-agent does it. But that is something
> for 2.1.

This seems like a good opportunity to bump my libassuan suggestions
[1]. I've dropped this while I'm waiting on some my gpgme
INPUT/OUTPUT handler patch [2], since I don't want to overwhelm you guys,
but I'm happy to get back to work if your're ready to start reviewing
my patches ;).

Cheers,
Trevor

[1]: http://lists.gnupg.org/pipermail/gnupg-devel/2012-April/026670.html
[2]: Which for some reason I cannot find in the archives on
http://lists.gnupg.org/pipermail/gnupg-devel/

--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

Attachments:

signature.asc (0.82 KB)

gniibe at fsij

Jun 24, 2012, 6:13 PM

Post #6 of 10 (201 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On 2012-06-22 at 10:25 +0200, Werner Koch wrote:
> On Fri, 22 Jun 2012 04:49, gniibe [at] fsij said:
>
> > I backported SCD (scdaemon) related changes to scd-backport-2-0
> > branch. If it doesn't have any problem, I'd like to merge it into
> > STABLE-BRANCH-2-0.
>
> I am fine with this. Shall I prepare a release candidate then?

I added one more change of following (I will add this change to master
branch too). Then, rebase and merge scd-backport-2-0 branch into
STABLE-BRANCH-2-0.

I think that changes fix problems, and has no regression. But, I
still have a concern about how scdaemon should run. I am writing
about this in the next mail.

commit 34b78c7d82f3923052e36d405ba403787ae9df16
Author: NIIBE Yutaka <gniibe [at] fsij>
Date: Sun Jun 24 10:45:49 2012 +0900

scd: handle reader/token removal.
* scd/apdu.c (pcsc_error_to_sw): PCSC_E_UNKNOWN_READER means
SW_HOST_NO_READER.

diff --git a/scd/apdu.c b/scd/apdu.c
index a343307..0ce1c51 100644
--- a/scd/apdu.c
+++ b/scd/apdu.c
@@ -841,6 +841,7 @@ pcsc_error_to_sw (long ec)
case PCSC_E_CANCELLED: rc = SW_HOST_ABORTED; break;
case PCSC_E_NO_MEMORY: rc = SW_HOST_OUT_OF_CORE; break;
case PCSC_E_TIMEOUT: rc = SW_HOST_CARD_IO_ERROR; break;
+ case PCSC_E_UNKNOWN_READER: rc = SW_HOST_NO_READER; break;
case PCSC_E_SHARING_VIOLATION: rc = SW_HOST_LOCKING_FAILED; break;
case PCSC_E_NO_SMARTCARD: rc = SW_HOST_NO_CARD; break;
case PCSC_W_REMOVED_CARD: rc = SW_HOST_NO_CARD; break;

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

gniibe at fsij

Jun 24, 2012, 6:30 PM

Post #7 of 10 (201 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

Thanks for your explanation about scdaemon. I understand the
background.

Let me explain my concern.

There is a use case for Gnuk Token like this:

(1) Use the token for OpenSSH authentication through gpg-agent as ssh-agent
(2) User inserts the token before login
(3) ... and remove the token after authentication

Currently, scdaemon keeps watching (and open and get status). In the
use case above, a user doesn't expect scdaemon keeps watching for
insertion. My concern is that this results shorter battery power life
for laptop.

For the use case above, a patch like following makes sense. The
scdaemon doesn't need to open by itself. Once it will be open by
another foreground thread, it will get status, and keep watching to
detect removal.

diff --git a/scd/command.c b/scd/command.c
index 227057e..a4b3c08 100644
--- a/scd/command.c
+++ b/scd/command.c
@@ -2200,11 +2200,6 @@ update_reader_status_file (int set_card_removed_flag)
int idx;
unsigned int status, changed;

- /* Make sure that the reader has been opened. Like get_reader_slot,
- this part of the code assumes that there is only one reader. */
- if (!slot_table[0].valid)
- (void)get_reader_slot ();
-
/* Note, that we only try to get the status, because it does not
make sense to wait here for a operation to complete. If we are
busy working with a card, delays in the status file update should

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

Jun 25, 2012, 2:32 AM

Post #8 of 10 (201 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On Mon, 25 Jun 2012 03:30, gniibe [at] fsij said:

> Currently, scdaemon keeps watching (and open and get status). In the
> use case above, a user doesn't expect scdaemon keeps watching for
> insertion. My concern is that this results shorter battery power life
> for laptop.

You mean, we should replace polling by a proper method to do so. IIRC,
it was not possible to do this with libusb or pcscd back when I wrote
it. On Linux we might find a way to sleep on reader changes; in general
I prefer portable solutions, though.

> For the use case above, a patch like following makes sense. The
> scdaemon doesn't need to open by itself. Once it will be open by
> another foreground thread, it will get status, and keep watching to

What foreground thread do you have in mind? A new one sleeping on
USB events?

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

gniibe at fsij

Jun 25, 2012, 6:17 PM

Post #9 of 10 (205 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On 2012-06-25 at 11:32 +0200, Werner Koch wrote:
> On Mon, 25 Jun 2012 03:30, gniibe [at] fsij said:
>
> > Currently, scdaemon keeps watching (and open and get status). In the
> > use case above, a user doesn't expect scdaemon keeps watching for
> > insertion. My concern is that this results shorter battery power life
> > for laptop.
>
> You mean, we should replace polling by a proper method to do so.

There are two things: (1) Polling for "get status" for existing
token and (2) Polling for detecting insertion of token.

Let me talk about latter, at first.

My question here is: Is polling for detecting insertion needed?

The patch I sent yesterday is to show this issue (for token insertion.
The patch is not yet complete to handle card insertion, though). Open
new connection will be done only by the thread of scd_command_handler
-> assuan_process (which I said "foreground"). After that, polling
will be done with "get status" for new connection.

With no polling of detecting insertion, status file will not be
updated immediately, script won't be executed immediately. It will
only updated and executed after user will do some action to use token.
But, it seems for me that it's OK.

> > For the use case above, a patch like following makes sense. The
> > scdaemon doesn't need to open by itself. Once it will be open by
> > another foreground thread, it will get status, and keep watching to
>
> What foreground thread do you have in mind? A new one sleeping on
> USB events?

In the previous mail, I talked about to stop polling for detecting
insertion, and "foreground thread" meant the one of
scd_command_handler, which accepts request from gpg-agent.

Let's talk about (1) Polling for "get status".

> IIRC, it was not possible to do this with libusb or pcscd back when
> I wrote it. On Linux we might find a way to sleep on reader
> changes; in general I prefer portable solutions, though.

There is no good general way other than polling to get status of
reader/token.

But, if CCID reader/token supports interrupt transfer for status, it
is possible to use this for it, instead of polling. Now, newer libusb
(libusbx.org) has support for event driven asynchronous model, it is
possible to use single interrupt transfer URB. I think that it is
portable, provided newer libusb is good enough for portability.

When CCID reader/token with interrupt transfer will be common, it will
be good to support this way, in future.

BTW, Gnuk does not (yet) support interrupt transfer.
--

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

gniibe at fsij

Jul 20, 2012, 12:48 AM

Post #10 of 10 (165 views)
Permalink

Re: scd-backport-2-0 branch [In reply to]

On 2012-06-25 at 10:13 +0900, NIIBE Yutaka wrote:
> I added one more change of following (I will add this change to master
> branch too). Then, rebase and merge scd-backport-2-0 branch into
> STABLE-BRANCH-2-0.

I forgot to test ccid-driver with Gnuk. Today, I found a problem and
I committed following change to STABLE-BRANCH-2-0. This is backport,
it has been in the master branch.

diff --git a/scd/ccid-driver.c b/scd/ccid-driver.c
index 5281a2f..49dde61 100644
--- a/scd/ccid-driver.c
+++ b/scd/ccid-driver.c
@@ -3129,6 +3129,7 @@ ccid_transceive_secure (ccid_driver_t handle,
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
+ case VENDOR_FSIJ: /* Tested with Gnuk (0.21). */
break;
case VENDOR_VASCO: /* Tested with DIGIPASS 920 */
pinlen_max = 15;
--

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads