From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Permissions on Sockets
Date: Wed, 19 Jan 2005 21:41:01 +0100 [thread overview]
Message-ID: <1106167261.8190.138.camel@pegasus> (raw)
In-Reply-To: <6DD9FBCE-69DB-11D9-A39A-000D9348D4BE@magnifeye.com>
Hi Jonathan,
> I am doing an inquiry of all devices, finding our device, connecting to
> it and the reading bytes via a rawsocket.
>
> The only issue I see so far is the writev command (I copied the code
> from hci_send_cmd).
>
> How do I assign root rights for this?
you need to change the HCI security filter inside the kernel or make
your application setuid root or adapt the capabilities of your program.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-19 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 19:24 [Bluez-users] Microsoft keyboad/mouse problem Dave Sailer
2004-12-09 21:27 ` Marcel Holtmann
2005-01-18 19:38 ` [Bluez-users] Permissions on Sockets Jonathan Sass
2005-01-18 23:56 ` Marcel Holtmann
2005-01-19 5:31 ` Jonathan Sass
2005-01-19 20:41 ` Marcel Holtmann [this message]
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=1106167261.8190.138.camel@pegasus \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox