Dear all,

As part of the preparation work to reorganize and give more power to the
community at large, we are happy to announce that we are setting up a
debugging server for OpenSC. 

This is not the QA farm, as QA an automated testing tool. The aim of the
debugging server is to give OpenSC main developers access to the most
popular smarcards in a debugging environment.

Some smartcards are hard to find or come in a developer version, for
example the Starcos SPK 2.3. Others are quite expensive, I wron't
comment. 

So IMHO it is better to do testing on a shared server.

So we plan to implement the following, advice is welcome:
* pcscd should be started in user mode and debug mode with output to log
file, upon user connection. Users are part of pcscd group, so they
should be able to access smartcards, kill and restart the daemon.
* If possible, I would like to restrict the number of concurrent
sessions in OpenSSH an set it to one. There should be no idle session.
If someone is already connected doing debugging, OpenSSH should reject
connection. This is the most tricky part of the settings as I have NO
IDEA how to achieve this. 
* What debugging/profiling tools do you need? gbd, what else?
* Anyone can ask for access, just write me jmpo...@gooze.eu. 
Access is free as in free beer.

As usual, donations of smartcards are welcome. We now need two cards
from the same vendor/type: one card for the QA farm, another for the
debugging server.

The first version of the debugging server will be online on Wednesday,
comments are welcome.

Let the force be with us!

Kind regards,
-- 
                  Jean-Michel Pouré - Gooze - http://www.gooze.eu

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to