Hi, I would like to welcome three developers to the project:
Joachim Astel has contributed valuable insight and code/patches to the project in the past. He has deployed OpenXPKI in his own environment and was successful in integrating a non-nCipher HSM. :) Arkadius Litwinczuk has been working in our team here for some time. Next year he will work on improving the SCEP server, the goal is to support the latest SCEP drafts, including the GetCACaps (get CA capabilities) commands, SHA1 and SHA2 support and challenge password implementation. He will also clean up the SCEP workflow to reflect the actual life cycle of a public key (which will hopefully prevent wasting superfluous workflow instances for failed SCEP requests). His work will also extend into the CertNanny project which we plan to extend to include support for secure Root CA certificate distribution. Andreas Leibl has joined our development team only recently. His tasks for next year will be extending the Workflow glue code with the goal of making OpenXPKI scalable and redundant by allowing multiple instances actively running at the same time (assumption: shared, redundant database). This might also involve adding mechanisms for handling stalled workflow instances. Welcome to the OpenXPKI! ** In the past two years we have been pretty busy with internal customization of OpenXPKI. For this project we created a whole new and user friendly frontend for a self-service Smartcard personalization and PIN unblocking solution. Due to the large number of environment dependencies (e. g. LDAP infrastructure and schema) it is not very easy to generalize the solution for upstream inclusion, but we will try to do so once we have a stable solution. This project resulted in few code changes in the upstream repository - but we are still actively working on the project. >From several years of running OpenXPKI in production we have now a pretty good >understanding of what is good and what is wrong with the project. We plan to >address some of the most important issues next year, including rethinking the >configuration layer, runtime behaviour (*cough* memory footprint *cough*), >database integration, clustering support and customization hooks. cu Martin ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
