Hi Viktor, Am Freitag 19 März 2010 15:10:29 schrieb Viktor TARASOV: > I would like to start to submit the support for the cards IAS/ECC as it > defined in 'Gixel' specification [1] . > File system of this card is based on PKCS#15.
good idea! go for it!:) > > This support should include multi-applications, secure messaging (SM), > external authentication (EA), qualified signature, ... > > Support of SM and EA will be implemented as a loadable module . This > module, relatively small, will have different versions. 'Local' version > will have direct access to the SM or EA key-sets and is used mostly for > tests. > 'Distant' version should communicate with some distant entity that is > able to 'securize' the APDUs or to generate secured APDUs . This > solution we are currently using in our PKI&SCM projects . will you publish both? I'm interested in both ways, too. maybe we could compile in the simple version, so the users don't need additional libs/plugins to make the card work, but allow an additional module to take precedence. > First one is to create some sub-project or brunch, forked from the > current trunk. Here we'll have possibility to finalize the basic > architecture features in inoffensive for the main brunch manner . I > cannot estimate how much efforts is needed to support one more > sub-project, and so, don't know if it's acceptable. > > Second is to start the integration into the main trunk. It will be > rather slow and somewhere 'painful' way. But it will not need the > support of another brunch/sub-project . I don't know what is the release > roadmap, but if that is 'the road we take', I guess it would be safe to > fix the actual state of trunk with the next (major ?) release . both is fine with me. if you want to evaluate a software that might help you: git for example has much better merge support than svn, as far as I know. and it provides a bridge to svn, so you can import svn in a git, then work in git, and push commits back into git (both branches and trunk). (hg or bzr might work as well, I think all of them have such svn bridges...) Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
