On Tue, Aug 14, 2007 at 07:46:20PM -0700, Siddhartha Kasivajhula wrote: > > Depending on your card OS this may be irreversible. :\ > > How about this command "unblock"? OpenSC says it can "unblock a > PIN". What is the format of this command? I tried: > unblock KEY1 111111 > unblock KEY1 11:11:11 > ..and many permutations of 00:11:11:11, 11:11:11:ff, > 00:00:00:00:00:11:11:11 > > they all return "Invalid type"
--unblock-pin is an option to pkcs15-tool. Try the short form: pkcs15-tool -u > > > entered "111111" as the user PIN. > > > > I would assume it's more like 31:31:31:31:31:31 but possibly it > > will need padding to 8 bytes with 00 or ff, before or after. > > did you choose "31" arbitrarily? No. 31 is the ascii code of '1' in hex. > 8 bytes -- so in my case something like "00:00:00:00:00:11:11:11" ? Possibly 00:00:31:31:31:31:31:31 or 31:31:31:31:31:31:00:00, but I'm not sure about the padding. All this knowledge already exists within OpenSC however, so it is much easier to just use the high-level pkcs15-tool. > > OpenSC [3F00]> verify KEY1 111111 > > > > opensc-explorer really is just a low-level software debugging > > tool, not intended for anyone but developers. > > Yes, I plan to develop :) Excellent! :) I suggest getting to know both cards and software using the high-level tools first, though. > > How do I unlock the card now? > > > > What card was this again? > > CRYPTO EGATE 32K Ok. Try pkcs15-tool -u I know for a fact you can at least erase it with pkcs15-init -EC (also creates a new pkcs15 structure, -C can be done separately) //Peter _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
