On Tuesday 25 April 2006 13:42, Chaskiel M Grundman wrote: > you can't pkcs15-init -C more than once. > if pkcs15-init -E worked on this card, you could do that first, but if your > card is anything like mine, there's a pin protecting DELETE on objects in > the MF (this card supports list files, and fetching acls (use the 'info' > command) in opensc-explorer, so you can verify this)
Is this also why I can't delete any key objects? I was testing object importing / deleting and now I've got a bunch of useless objects all named "deleted" but not actually gone. > the opensc tools only let you set them at token initialization time. Great, so I can never change these? > > Do I really have a pin? I wasn't even prompted for it when I imported > > the cert. > > You do not have a pin. pkcs15-init -P creates pin objects. pkcs15-init says I need to pass an id for the pin. What is the id for? > the siemens application is not pkcs15 compatible. These pins are for that > app (which is in 3F00:3000 or something like that and was already partially > initialized, unlike the ITSEC-P's app). > > cardos has "local" (DF specific) pins, so the default pins and the opensc > pins will not interfere with each other. Wouldn't it be better for opensc to use the cardos pins? -Justin _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
