Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)

[Marcel Holtmann <marcel@holtmann.org>]

Hi Paul,

> Another big concern I'm having is about security, most hciconfig
> commands require 'higher than normal' privileges to execute, should
> the daemon allow certain requests only to the root user ? (luckily
> dbus was conceived with security in mind, so adding such a policy
> would not be difficult).
> This would just make things more complicated and I don't think there's
> any real gain in doing so, but maybe there are some security issues I
> ignore at the moment, let me know your opinion.
> (if for example, a program calls ListDevices to list the adapters, and
> the user wants to use an interface which is not active, should the
> program be allowed to bring it up?)

the bluetoothd run with root (or chroot) rights and thus it needs to
provide its own security policy.

> What if two (or more) applications chose, for whatever reason, to set
> a different default adapter? If you *really* want such a mechanism,
> maybe you should make such a method callable only by authorized code
> (hence my dilemma above) or simply select the default adapter
> internally in the daemon and don't expose this method at all.

as I said in the previous answers, the setting which is the default
adapter must go through the kernel.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel