From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: From: Claudio Takahasi To: bluez-devel@lists.sourceforge.net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Subject: [Bluez-devel] Device configuration permissions Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 31 Oct 2005 15:19:55 -0200 Hi Marcel, There is a open issue that we need define. I was talking with Eduardo and Johan in the IrC channel about how design the Devices services and handle security. In our opinion read services should be available to all users and write service should be restricted. We have a lot of ways to define D-Bus rules, use path, interface, method name, user and/or a combination of these parameters. Define method name rules, can make the maintenance hard. The easiest way is use interface to define rules. Here are some interface names suggestions: Suggestion 1: org.bluez.Devices.Public org.bluez.Devices.Protected Suggestion 2: org.bluez.Devices.admin org.bluez.Devices.user Do you agree with this approach of define different interfaces? If yes, do you have another suggestion for the interface name? Regards, Claudio -- --------------------------------------------------------- Claudio Takahasi Instituto Nokia de Tecnologia - INdT ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel