From: "Thor Egil Skaug" <paxtonrd@hotmail.com>
To: "'TM'" <bluez@gammah.com>, <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Socket permissions
Date: Mon, 1 Mar 2004 08:13:34 -0800 [thread overview]
Message-ID: <000501c3ffa8$255baee0$46a57e40@thores> (raw)
In-Reply-To: <40435E1B.7000900@gammah.com>
>I did
># chown root hciconfig
># chmod 4711 hciconfig
>
>which sets that program setUID root. This should solve that problem,
but setting programs setuid root *could* cause a problem for security.
Since all my bluez stuff is on a laptop that's rarely online, the risk
is negligible for me.
>
>-t.
Thanks, but this is not what I meant. The application that I am writing
(using raw-data hci sockets) should not require any
different permissions or owner. What I am looking for is a way to let a
normal user run my application that has normal permissions and
open a BlueZ hci socket.
An example is using the serial port in an application. To allow users to
run such a program, one would have to set permissions
on /dev/ttyS*.
Thor
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-01 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 15:48 [Bluez-users] Socket permissions Thor Egil Skaug
2004-03-01 16:00 ` TM
2004-03-01 16:13 ` Thor Egil Skaug [this message]
2004-03-01 16:17 ` Marcel Holtmann
[not found] <BAY1-F110eiS609lcQt00003ec7@hotmail.com>
2004-03-01 17:27 ` 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='000501c3ffa8$255baee0$46a57e40@thores' \
--to=paxtonrd@hotmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=bluez@gammah.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox