Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: GnuPG: users

How to enable the reader's keypad

 

 

GnuPG users RSS feed   Index | Next | Previous | View Threaded


tux.tsndcb at free

Oct 8, 2009, 10:46 AM

Post #1 of 5 (819 views)
Permalink
How to enable the reader's keypad

Hi,

I'm using gnupg2 2.0.13 (with libccid on my debian) and a smardcard reader with keypad, but code PIN is always ask on my desktop, not on the reader.
On my scdaemon.conf I've not disable-keypad
So how to do this ?

Thanks in advanced for your answer.

Best regards

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


wk at gnupg

Oct 13, 2009, 1:05 AM

Post #2 of 5 (726 views)
Permalink
Re: How to enable the reader's keypad [In reply to]

On Thu, 8 Oct 2009 19:46, tux.tsndcb [at] free said:

> On my scdaemon.conf I've not disable-keypad
> So how to do this ?

The keypad is only enabled for certain readers:

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.

Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.


Shalom-Salam,

Werner


--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


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


tux.tsndcb at free

Oct 13, 2009, 2:14 AM

Post #3 of 5 (724 views)
Permalink
How to enable the reader's keypad [In reply to]

Hi Werner,

I have add this yesterday in the ccid-driver.c file :

/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};

and

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

But it doesn't works, I've give more information in the [issue1148]

perhaps it because my conf file are wrong :

gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net

gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800

scdaemon.conf :
verbose


and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent


Thank in advanced for your confirmation.

Best Regards


----- Mail Original -----
De: "Werner Koch" <wk [at] gnupg>
À: "tux tsndcb" <tux.tsndcb [at] free>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad

On Thu, 8 Oct 2009 19:46, tux.tsndcb [at] free said:

> On my scdaemon.conf I've not disable-keypad
> So how to do this ?

The keypad is only enabled for certain readers:

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.

Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.


Shalom-Salam,

Werner


--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


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


tux.tsndcb at free

Oct 13, 2009, 10:10 AM

Post #4 of 5 (724 views)
Permalink
How to enable the reader's keypad [In reply to]

Hi Werner,

the Vendor tell to me than I need also this for the reader, but I dont know where to put it :

bNumberMessage = 0x01
bEntryValidationCondition = 0x02
bNumberMessages = 0x03

Thanks in advanced for your return

Best Regards

----- Mail Original -----
De: "tux tsndcb" <tux.tsndcb [at] free>
À: "Werner Koch" <wk [at] gnupg>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 11h14:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad

Hi Werner,

I have add this yesterday in the ccid-driver.c file :

/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};

and

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

But it doesn't works, I've give more information in the [issue1148]

perhaps it because my conf file are wrong :

gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net

gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800

scdaemon.conf :
verbose


and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent


Thank in advanced for your confirmation.

Best Regards


----- Mail Original -----
De: "Werner Koch" <wk [at] gnupg>
À: "tux tsndcb" <tux.tsndcb [at] free>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad

On Thu, 8 Oct 2009 19:46, tux.tsndcb [at] free said:

> On my scdaemon.conf I've not disable-keypad
> So how to do this ?

The keypad is only enabled for certain readers:

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.

Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.


Shalom-Salam,

Werner


--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


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

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


tux.tsndcb at free

Oct 14, 2009, 12:41 PM

Post #5 of 5 (712 views)
Permalink
Re: How to enable the reader's keypad [In reply to]

Hi Werner,

Do I need to change also something in this two files :

agent/divert-scd.c

scd/app-dinsig.c

Is there a commande line to test reader's keypad acces ?

thanks in advanced for your return.

Best Regard
----- Mail Original -----
De: "tux tsndcb" <tux.tsndcb [at] free>
À: "Werner Koch" <wk [at] gnupg>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 19h10:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad

Hi Werner,

the Vendor tell to me than I need also this for the reader, but I dont know where to put it :

bNumberMessage = 0x01
bEntryValidationCondition = 0x02
bNumberMessages = 0x03

Thanks in advanced for your return

Best Regards

----- Mail Original -----
De: "tux tsndcb" <tux.tsndcb [at] free>
À: "Werner Koch" <wk [at] gnupg>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 11h14:32 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: How to enable the reader's keypad

Hi Werner,

I have add this yesterday in the ccid-driver.c file :

/* We need to know the vendor to do some hacks. */
enum {
VENDOR_CHERRY = 0x046a,
VENDOR_SCM = 0x04e6,
VENDOR_OMNIKEY= 0x076b,
VENDOR_GEMPC = 0x08e6,
VENDOR_KAAN = 0x0d46,
VENDOR_COVADIS= 0x0982
};

and

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
case VENDOR_COVADIS: /* In Testing with VEGA-ALPHA. */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

But it doesn't works, I've give more information in the [issue1148]

perhaps it because my conf file are wrong :

gpg.conf :
use-agent
utf8-strings
keyserver hkp://keys.gnupg.net

gpg-agent.conf :
verbose
pinentry-program /usr/bin/pinentry-gtk-2
no-grab
default-cache-ttl 1800

scdaemon.conf :
verbose


and gpg-agent is invoked by STARTUP="$GPGAGENT --daemon --sh --write-env-file=$PID_FILE $STARTUP" in the file /etc/X11/Xsessions.d/90gpg-agent


Thank in advanced for your confirmation.

Best Regards


----- Mail Original -----
De: "Werner Koch" <wk [at] gnupg>
À: "tux tsndcb" <tux.tsndcb [at] free>
Cc: gnupg-users [at] gnupg
Envoyé: Mardi 13 Octobre 2009 10h05:31 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: How to enable the reader's keypad

On Thu, 8 Oct 2009 19:46, tux.tsndcb [at] free said:

> On my scdaemon.conf I've not disable-keypad
> So how to do this ?

The keypad is only enabled for certain readers:

/* We have only tested a few readers so better don't risk anything
and do not allow the use with other readers. */
switch (handle->id_vendor)
{
case VENDOR_SCM: /* Tested with SPR 532. */
case VENDOR_KAAN: /* Tested with KAAN Advanced (1.02). */
break;
case VENDOR_CHERRY:
/* The CHERRY XX44 keyboard echos an asterisk for each entered
character on the keyboard channel. We use a special variant
of PC_to_RDR_Secure which directs these characters to the
smart card's bulk-in channel. We also need to append a zero
Lc byte to the APDU. It seems that it will be replaced with
the actual length instead of being appended before the APDU
is send to the card. */
cherry_mode = 1;
break;
default:
return CCID_DRIVER_ERR_NOT_SUPPORTED;
}

You may add you vendor id (scd/ccid-driver.c) and test it. Let me know
if that works and I will add the reader.

Further we don't support them when using PC/SC. At the time I added the
support PC/SC had no standard for using the keypads.


Shalom-Salam,

Werner


--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


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

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

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

GnuPG users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.