http://bugzilla.moblin.org/show_bug.cgi?id=6376
--- Comment #20 from jku <jku(a)linux.intel.com> 2010-02-10 08:41:45 PST ---
The same branch now includes my client implementation. It's very simple:
* only responds if the request is from a session started by itself.
This can be changed if you like (but see below)
* doesn't close the dialog if another client is handling the request
I think for the next API iteration we need to look at how DBus password
handling is done elsewhere -- this isn't very nice from security POV. Not that
this is any less secure than writing the password in the config file, but the
password prompt might lead the user to think it is...
Possible issues with server implementation:
The request params don't seem to include the configuration name, and while
session path does give me a way to get the configuration, I don't think I can
get the name from there (I can query the PeerName property, but that's not
always defined). This doesn't affect current implementation (as I only accept
sessions I started) but a generic password request handling can't be done...
It seems the sync continues with an empty password if I set an empty hashtable
(no password) as the return value. I think it should end with LOCERR_USERABORT
or a new status value.
Should I file new bugs for these?
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.