public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [DBUS] Service Agent Security
Date: Sun, 03 Dec 2006 15:04:17 +0100	[thread overview]
Message-ID: <1165154657.19590.49.camel@localhost> (raw)
In-Reply-To: <e1effdeb0611280457p51b5b9a4vdd003eb8e5f4efab@mail.gmail.com>

Hi Claudio,

> In the new service interface, hcid will work as a proxy routing
> messages from/to clients to service agents. We added verifications
> based on the message sender field in the hcid, but it is missing add
> some security verification in the service agent side.  If someone
> wants to send a message directly to the service agent it is possible!
> eg:
> dbus-send --system --dest=":1.5" --type=method_call --print-reply
> /org/bluez/service_agent_12094 org.bluez.ServiceAgent.Start
> 
> I started the investigation how avoid clients send messages directly
> to the Service Agents. I don't think it's possible add rules in the
> /etc/dbus-1/system.d/bluetooth.conf file to block that. Do you know
> how create this rule? It is possible? (As long as I can remember our
> last discussion, service agents will not have D-Bus configuration
> files.)
> 
> Another option is let the Service Agent check this, I mean extract the
> sender and only accept message from the hcid. We have the same problem
> with authorization and passkey agents.
> 
> Comments? Is it really necessary check this or we can leave it open?

I don't know how to create the rule, but the agent implementation should
not be bothered at all. If we need to have a config file per agent, then
this is also not a big problem. An agent that is serious about security
will implement such config file.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-12-03 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 12:57 [Bluez-devel] [DBUS] Service Agent Security Claudio Takahasi
2006-12-03 14:04 ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1165154657.19590.49.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox