OpenPGP card tests 1.3.6

Thomas Schorpp t.schorpp at gmx.de
Mon Jun 7 20:49:16 CEST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Werner Koch wrote:
| On Fri, 23 Jan 2004 05:25:50 +0100, thomas schorpp said:
|
|
|>is full charset handled for PINs or only numbers ?
|
|
| Bye definition the PIN should be UTF-8 encoded, thus all characters
| except for 0x00 are allowed. For pragmatic reasons I'd suggest to use
| ASCII only for now - at least for the Admin PIN.
|
|   Werner
|

ok, first 2 issues:

C001-L1: "No typing verification on pin entries in --edit-card >passwd,
dangerous..."

C002-L3: "gpg needs to be restarted to verify unblocked pin retry
counter - >list shows false count 0 instead of 3 without"

(proceeding further provocation test)
...

i could fix that, if im allowed(?)

y
tom


tom1:/usr/local/src/gnupg-1.3.6# gpg --card-edit --allow-admin

gpg: DBG: asking for PIN 'New PIN'

New PIN
PIN unblocked and new PIN set.

Admin PIN
gpg: DBG: asking for PIN 'New Admin PIN'

New Admin PIN
PIN changed.

Command> list

Application ID ...: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Version ..........: 1.0
Manufacturer .....: PPC Card Systems
Serial number ....: 000000xx
Name of cardholder: thomas schorpp
Language prefs ...: de
Sex ..............: male
URL of public key : [not set]
Login data .......: [not set]
Signature PIN ....: not forced
Max. PIN lengths .: 254 254 254
PIN retry counter : 0 3 3		
xxxxxxxxxxxxxxxxxxxx^
should be 3 at this time.













-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAxLis1L8Hg/0A/fwRAmM4AJ4nd+QxmIxioTwgFKewx9yhVOsJegCeLwl3
rzkFliyU6MLb0dQ3Z9mlaq0=
=qOBS
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list