{5} Assigned, Active Tickets by Owner (Full Description) (6 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

joao (1 match)

Ticket Summary Component Milestone Type Severity Created
Description
#400 [PTeID] Error accessing "Citizen Data" data object opensc defect blocker 11/07/11

Hello im trying to read the "Citizen Data" on my PTeID using pkcs15-tool and it fails, its an PIN protected object, and im supplying the correct pin. Im not sure if i can read the object using the pkcs15-tool, it also fails reading the open/nopin required "Citizen Data" but succeeds reading the also open/nopin "Citizen Notepad" data object ....

Can someone help me ?

Thanks in advance

martin (4 matches)

Ticket Summary Component Milestone Type Severity Created
Description
#70 Document NSS/Mozilla and NonRepudiation issue pkcs11 task normal 02/15/06

 http://groups.google.com/group/mozilla.dev.tech.crypto/browse_frm/thread/104fe27c63063caa/a7a5cbf5b34645a3#a7a5cbf5b34645a3

#323 Remove hard dependency on libltdl in favor of direct native API. opensc 0.12.3 enhancement normal 02/03/11

This greatly simplifies building on Windows (drops one external dependency) and allows to build on platforms where libltdl is not (readily) available, while still favoring libltdl on platforms where the dependency is not a burden.

  • shift libpkcs11 from src/pkcs11 to src/common as it is not used to implement the OpenSC PKCS#11 module
  • invent a "libscdl" mini library that implements either libltdl based dynamic loading or uses native interfaces
  • drop hard requirement for libltl to build OpenSC
  • native Windows build does not need libltdl any more
  • specify CNGSDK include dir to find cardmod.h (only registers with a handful of Visual Studio versions)

See opensc-devel for background info:  http://www.opensc-project.org/pipermail/opensc-devel/2011-January/015805.html

#371 pkcs11-tool includes CKA_MODULUS_BITS when writing an RSA public key object, fails with CKR_TEMPLATE_INCONSISTENT pkcs11-tool 0.12.3 defect normal 06/19/11

Using an eToken 72K with Aladdin 5.1 drivers, writing an RSA public key object with the following command 

pkcs11-tool.exe --module c:\WINDOWS\system32\etpkcs11.dll -l -w pub.der -y pubkey --id 1001 --label test

gives the error: 

Using slot 0 with a present token (0x0)
Logging in to "eToken".
Please enter User PIN: error: PKCS11 function C_CreateObject failed: rv = CKR_TEMPLATE_INCONSISTENT (0xd1)

Writing private key, certificate objects and creating key pairs work.

According to the PKCS11 document, the attribute CKA_MODULUS_BITS "Must not be specified when object is created with C_CreateObject". The included patch removes the CKA_MODULUS_BITS attribute from the template when creating RSA public key objects.

#111 Document how to change a PUK code with pkcs15-tool documentation enhancement minor 10/30/06

Documentation needs to mention how to change a PUK code until we'll have a foolproof --change-puk option in pkcs15-tool.

nils (1 match)

Ticket Summary Component Milestone Type Severity Created
Description
#59 Warning regarding not-erasable cards in Quickstart pkcs15init defect normal 11/13/05

The  Quick Start Guide of SCB states:

Erase your card, if something failed 

pkcs15-init --erase --use-default-transport-key

The OpenSC SecureSetup? says:

However,anyone knowing the transport key and who has access to your card can delete the pkcs15 directory with all its keys, certs, data, ...

This is not true for all cards. There should be a warning regarding cards that are not erasable. Maybe a list of cards known to be not erasable or a hint how to test ones card. In that case, you must not loose your SO-PIN and -PUK, even if you just want to test the card/software. I dont know if its possible to delete single objects on such cards. If not, the warning should also say so. Useless test keys/certs own a rather expensive card would be annoying. An unsuspecting user could discard his PINs/PUKs just to realize that he cant erase the card.

Note: See TracReports for help on using and creating reports.