All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Preyss" <nalp@gmx.net>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] ciptool setuid
Date: Fri, 30 Apr 2004 10:28:48 +0200	[thread overview]
Message-ID: <20040430082848.GA30282@gmx.net> (raw)
In-Reply-To: <1083278666.4000.130.camel@pegasus>

On  0, Marcel Holtmann <marcel@holtmann.org> wrote:
> > In debian members of group dip and dialout and use modem/isdn devices.
> > Unfortunately it looks like that one need to be root to run ciptool
> > and make the isdn controler via bluetooth available.
> 
> everybody with CAP_NET_ADMIN can create or release a CIP device.

But with this capability he gains a lot of right about any kind of net
traffic and devices. So I personally think, using sudo with a predefined set of
allowed arguments is a more secure way.

nicholas


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-04-30  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 20:30 [Bluez-users] ciptool setuid Achim Bohnet
2004-04-29 22:35 ` Nicholas A. Preyss
2004-04-29 22:44 ` Marcel Holtmann
2004-04-30  8:28   ` Nicholas A. Preyss [this message]
2004-04-30  7:56     ` Marcel Holtmann

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=20040430082848.GA30282@gmx.net \
    --to=nalp@gmx.net \
    --cc=bluez-users@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.