On Wed, Jan 7, 2009 at 6:41 PM, Marcel Holtmann <mar...@holtmann.org> wrote: > > that is exactly how it works and we can't use signal. Even directed > signal are not working since the method call into the agent has to > return the result or an error. > > What problem do you guys actually have with this? The agent inside > bluez-gnome is verifying that the method comes from the daemon it > registers its agent with and thus there is not even a security issue > here with trying to send arbitrary method calls to the UI.
I talked with davidz about this on IRC in a bit more high bandwidth mode; he's doing something similar with PolicyKit. I think if the rule is of the form: <allow send_interface="org.bluez.Agent" send_path="/org/bluez/Agent"/> that's probably fine. It does allow any process to send any message with that interface and path to any other, but we're in a similar situation with signals anyways right now. I wouldn't call it a problem even if it's just an <allow send_interface>, but ideally we don't have many of these since they're not as strong as <allow send_destination>. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
