Gabriele Turchi wrote:
> I was able to do also some secure operation directly on the card (I must
> check my code), but I wasn't able to fully understand the structure of a
> card driver: there are so many cross references between different parts
> of the libraries...
I've started working on this. At the moment, I have parts of
opensc-tool and opensc-explorer working (serial number, directory list,
file info, get file, things like that).
I'm now trying to get the pkcs15-tool to list the data objects. I've
managed to coax that through to where it is starting to read the
certificate and key directory files, where it is currently failing
because the directory files are not in a format that the current code
understands. It seems as if I'm a fair distance from cryptographic
operations, though I suppose it is hard to tell.
I'll post a separate message about my progress later, in the hope that
someone can cross-check what I've done so far.
In the meantime, if you have any code that did anything useful on the
card, whether inside opensc or not, I'd appreciate being able to see it.
> I also have some ACOS5 blank cards and some Windows/PKCS#11 formatted
> ones. This filesystem appear enough standard to maintain it, and ACOS5
> OS offer a "dir" command to investigate the card.
The PKCS#15 file system on these cards appears to be a little
non-standard, to say the least, or at least simply different to what the
current code knows how to support. I don't know whether the right
approach is going to be to just tweak the existing opensc generic
PKCS#15 layer, or to write a complete emulation layer instead. That
would be a shame, as I think I'd end up duplicating a lot of the
existing code in another module.
-- Ian
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
