Hi Colin,
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
On Mon, 05 Jan 2009 at 23:32:50 +0100, Filippo Giunchedi wrote:
On Mon, Jan 05, 2009 at 08:32:58PM +, Simon McVittie wrote:
allow send_interface=org.bluez.Agent/
That will work but is not ideal; D-Bus upstream opinion seems to be that
a bare send_interface without a
On Wed, Jan 7, 2009 at 2:17 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
Unfortunately they don't a well known service name nor object path, agents
are
user-registered
Never mind. We have a lot of these rules in the archive anyway
On Wed, 07 Jan 2009 at 14:45:37 -0500, Colin Walters wrote:
On Wed, Jan 7, 2009 at 2:17 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
Unfortunately they don't a well known service name nor object path, agents
are
user-registered
Never mind. We have a lot of these rules in
On Wed, Jan 7, 2009 at 3:09 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
As far as I can tell, BlueZ agents work like this:
* the agent (a UI process run by a user) calls a method on the hci daemon (run
by root) and passes in its unique name and its (arbitrary) object path
*
On Wed, Jan 07, 2009 at 07:17:35PM +, Simon McVittie wrote:
On Mon, 05 Jan 2009 at 23:32:50 +0100, Filippo Giunchedi wrote:
On Mon, Jan 05, 2009 at 08:32:58PM +, Simon McVittie wrote:
allow send_interface=org.bluez.Agent/
That will work but is not ideal; D-Bus upstream
On Wed, 07 Jan 2009 at 22:55:56 +0100, Filippo Giunchedi wrote:
On Wed, Jan 07, 2009 at 07:17:35PM +, Simon McVittie wrote:
Please go ahead with the unstable upload, but also attach the resulting
bluetooth.conf to this bug so I can review it.
attached, note that I used
On Wed, 07 Jan 2009 at 15:26:31 -0500, Colin Walters wrote:
On Wed, Jan 7, 2009 at 3:09 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
As far as I can tell, BlueZ agents work like this:
Urf. Can we just change this to use signals? Signals can be sent to
a particular
On Wed, Jan 7, 2009 at 6:25 PM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
As a solution for the current release of BlueZ, assuming that rethinking
the Agent API completely is not an option, does the proposed policy at
Hi Colin,
As far as I can tell, BlueZ agents work like this:
* the agent (a UI process run by a user) calls a method on the hci daemon
(run
by root) and passes in its unique name and its (arbitrary) object path
* later, the hci daemon calls a method on the agent
so the only
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?
On Sun, Jan 04, 2009 at 01:29:44AM +, Simon McVittie wrote:
Package: bluez-utils
Version: 3.36-2
Severity: serious
Justification: blocker for #503532 (CVE-2008-4311) and far-fetched security
hole
Tags: fixed-upstream
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags:
tags 510644 - fixed-upstream
thanks
On Sun, 04 Jan 2009 at 14:27:33 +0100, Filippo Giunchedi wrote:
I have tried with the experimental version of dbus and the said bluetooth.conf
file and it doesn't seem to work, though I'm investigating.
Thanks. You might get better debug logging with my
13 matches
Mail list logo
