Thanks for the update.
I'll be looking at building and adding packaging within the next day or
so.
I'll also take a look at how it works using Orca for accessibility. (If
it doesn't work that's not a big deal right now: it's just that is how I
use Gnome so I'll end up testing that )
>>>>> "Javier" == Javier Jardón <[log in to unmask]> writes:
Javier> Hello all, only a little update about the status of the UI.
Javier> The interface is almost done, including the search filter
Javier> and the dialogs to add/remove id cards. To store the info
Javier> about the idcards we decided to use a GKeyFile in the
Javier> XDG_DATA_HOME directory.
I'm a bit confused: on our first call, we decided that the phase 1
format of the data exported about the ID cards would be a file with two
lines of text: the first line would be a username; the second line would
be a password. That was the original call with Rob, Josh, myself and
another person from the Codethink business side. (I want to stress that
for the phase with a file in the home directory, only one ID card is
supported.)
Luke ended up assuming that file was called .gss_eap_id in the home
directory; that was discussed on this list and documented in the
mech_eap README.
With regard to the dbus stuff, I assume that you're talking about the
RPC between the UI and the GSS EAP mechanism.
It's my understanding that you're responsible for both sides of this
RPC: in particular you are responsible for C library client stubs that
mech_eap will call into (Luke is responsible for modifying mech_eap to
call these) and that you're responsible for the server implementations
within the UI.
First I'd like to confirm that my understanding of the interface
boundary is correct.
If so, I'd appreciate you sending out proposed documentation
for the C library so we can review the interface.
Also, on the original call we'd discussed that dbus almost certainly was
not appropriate for the Windows RPC interface. What are you going to
use on Windows? We need to get sufficient details on that in order for
Alexey to review them.
|