From: Achim Bohnet <ach@mpe.mpg.de>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] ciptool setuid
Date: Thu, 29 Apr 2004 22:30:07 +0200 [thread overview]
Message-ID: <200404292230.08106.ach@mpe.mpg.de> (raw)
Hi,
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.
Question: Are there other methods to enable members of group dialout
to use ciptool that making it setuid root? If not is it safe to
install ciptool by default like
=2Drwsr-x--- 1 root dialout 8368 2004-01-26 23:22 /usr/bin/cipt=
ool
So all group member of dialout can run it. All capi devices are
accessible by dialout members:
# l /dev/capi*
crw-rw---- 1 root dialout 68, 0 2004-03-22 14:00 /dev/capi20
crw-rw---- 1 root dialout 68, 1 2004-03-22 14:00 /dev/capi20.00
crw-rw---- 1 root dialout 68, 2 2004-03-22 14:00 /dev/capi20.01
=46rom a look at the usage/source it seem that ciptool really only allows
to 'create'/'release' a capi controlers.
Achim
=2D-=20
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- reddy@lion.austin.ibm.com
-------------------------------------------------------
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
next reply other threads:[~2004-04-29 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 20:30 Achim Bohnet [this message]
2004-04-29 22:35 ` [Bluez-users] ciptool setuid Nicholas A. Preyss
2004-04-29 22:44 ` Marcel Holtmann
2004-04-30 8:28 ` Nicholas A. Preyss
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=200404292230.08106.ach@mpe.mpg.de \
--to=ach@mpe.mpg.de \
--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.