Hi Guys, As you already heard (to death?), I'm working on a "smarter smart card" which (with my definition) is a cryptographic module explicitly designed for on-line enrollment over the web [1].
Anyway, since my core competence is architecture as well as due to limited funding the low-level part is a true challenge so I need to "cut some corners" to not get stuck. One possible solution seems to be reusing existing OS-drivers like CCID and PC/SC. My questions to you *real* experts out there are: 1. Would extended APDUs be a suitable way supporting a completely "alien" API? 2. What would be a good choice of emulation targets (USB reader+card) for not having to write a single-line of OS-dependent code or custom installation scripts? 3. Does existing drivers (P11s, CSPs) actually support any number of keys? Although writing the device code is non-trivial, compared to grasping Windows driver framework etc. it seems fairly reasonable, at least if you are equipped with an USB line-analyzer and some useful emulation targets. Ideally , there would be a "composite" USB interface where legacy systems would use CCID while newer systems would talk "native SKS". Provisioning can only use the latter. thanx, Anders 1] "Appendix A. KeyGen2 Proxy" in: http://webpki.org/papers/keygen2/sks-api-arch.pdf _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
