From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Device configuration permissions
Date: Mon, 31 Oct 2005 20:02:35 +0200 [thread overview]
Message-ID: <20051031180235.GA10264@localhost.localdomain> (raw)
In-Reply-To: <1130779899.5848.28.camel@blade>
Hi Marcel,
On Mon, Oct 31, 2005, Marcel Holtmann wrote:
> sorry, but both are the wrong approaches. I don't wanna dictate the
> security settings through the interface names and especially not with
> keywords like "admin", "protected" etc. This is the wrong approach and
> makes the interface really horribly, because the user shouldn't care
> that much about it.
IMHO it would make it easier for the user to understand why some method
doesn't work for him if the interface name had e.g. "admin" in it. I
don't see how that makes the interface "horrible".
> If our D-Bus rules file get big then this is the price we have to pay
> for a nice clean interface. And I am gladly to paying this price then.
So having a rule for each method is ok? This is quite easily doable in
the config file (although the file will become bigger and more difficult
to maintain).
Johan
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-10-31 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 17:19 [Bluez-devel] Device configuration permissions Claudio Takahasi
2005-10-31 17:31 ` Marcel Holtmann
2005-10-31 18:02 ` Johan Hedberg [this message]
2005-10-31 18:23 ` Marcel Holtmann
2005-10-31 18:26 ` Johan Hedberg
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=20051031180235.GA10264@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.