> ----Mensaje original---- > De: ludovic.rouss...@gmail.com > Fecha: 24/06/2011 14:13 > Para: <opensc-devel@lists.opensc-project.org> >Asunto: Re: [opensc-devel] About ticket #232 (portable gui) > >Hello, > >2011/6/24 jons...@terra.es <jons...@terra.es>: >> I'm working around ticket #232[1], (GUI related functions), but need a >> consensus about >> what is exactly needed [2] >> >> - At least two functions are required >> * Enter pin >> * Confirm Operation >> * ¿Any other? >Please do not code GUI inside OpenSC. I propose to use pinentry [1] instead. >A GUI application is already available for GTK+, KDE and Mac OS X. I >don't know about Windows. The idea - according to roadmap[1], #232 and my talks with Martin is to provide a separate library for GUI related functions. This library should be OS independent (by showing an unified interface for every OS) and use the less external libraries as possible >We already discussed about using pinentry. Is there a problem with >this solution? Well, in theory Windows (at least Vista and W7) and MacOS native functions provide a securized channel between GUI and opensc, and do not rely on external libraries There is no such functionality for Linux. Certainly there is support for Pinentry in Win and Mac, but these implementations requires extra work for getting and installing external libraries. IMO, it's better to use native calls when possible So the problem comes in Linux. - OpenDNIe uses pinentry in a fork+pipe scheme. This avoid need to link OpenSC against libassuan and libgpg-error - There are several pinentry variants. So need to create an extra configuration menu in /etc/opensc.conf to get proper path to desired pinentry app, and extra logic to detect presence and validity of configuration data Martin proposed me to study the use of gnome-keyring to handle UI in Linux That's is the current state. I'm next to start a branch to create separate GUI routines and need to get a clear idea on what is needed and how to implement. Juan Antonio [1] http://www.opensc-project.org/opensc/roadmap BTW: Martin: I'have my (new) MacMini ready to be used on Autobuilds for Mac... waiting instructions :-)
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
