On Tue, 2010-11-02 at 21:37 +0000, Mr Dash Four wrote: > >> 1. Generate a key file. I used: > >> - dd if=/dev/random of=~/master-key bs=1 count=2048 > >> - dd if=~/master-key of=~/key256 bs=1 count=256 > >> - dd if=~/master-key of=~/key512 bs=1 count=512 seek=256 > >> - dd if=~/master-key of=/key1k bs=1 count=1024 seek=768 > >> > > > > For what kind of algorithm are these keys? They are very large. > > > They all get hashed (sha512 I think), so as long as the data stream is > larger than 32 bytes that's good enough. I am aware that the keys are > quite large - this is just for testing for the time being. The actual > keys will be about 64 bytes long, no more than that. > > > > OK, I'm using almost the same command: > > > > pkcs15-init -W CIAInfo.bin --application-id "1.2.3" -l "MyObject" -a 01 > > > Does it work properly? Do you get it to list the data?
Opensc-explorer shows me the content of CIAInfo.bin without pin-verification. Does that answer your question? > >> I am using the version I've downloaded and compiled as per your kind > >> instructions. I think I downloaded it from the main OpenSC project site > >> (though from what I remember the links were messed up somewhat and even > >> though the link on the page was telling me that I am downloading the > >> newest version the actual .tar.gz file was for a version, which was 2 or > >> 3 revisions old so I had to go directly to the ftp server to do it). > >> > > > > You are using the latest official release, which is 0.11.13 > > (opensc-explorer states that). But development goes on in a version > > called trunk. Someday in the future, trunk will become the next official > > release. For your purpose using 0.11.13 is fine. But if you want to test > > trunk, then execute: > > > > svn co http://www.opensc-project.org/svn/opensc/trunk opensc > > > I know what trunk is (I am a developer too you know!). I will clone the > latest source (not least to get it with your latest patch applied - the > very reason I replied to your initial post, which started this thread!), > though, for the time being the version I am using is good enough (I also > created a patch on my own to pkcs11-tool to get rid of the prompt via an > additional option as it was messing up the output from plymouth). Sorry, I forgot. There was to much discussion on command line tools in this thread. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel