[Bug 222555] New: Grant access to /dev/rfcomm* for "desktop user"
https://bugzilla.novell.com/show_bug.cgi?id=222555 Summary: Grant access to /dev/rfcomm* for "desktop user" Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: seife@novell.com ReportedBy: dgollub@novell.com QAContact: qa@suse.de CC: security-team@suse.de In 10.1 there was udev rule to modify permission of the rfcomm device node (not by default): (bluez-utils) # uncomment this if you have configured an automatic rfcomm-bind in # /etc/bluetooth/rfcomm.conf # KERNEL=="rfcomm*", NAME="%k" GROUP="uucp" MODE="0660" OPTIONS="resmgr" Is it possible to do something similar for 10.2 by default for the "desktop user"? (jfyi: the OpenSync plugin moto-sync requires direct access to /dev/rfcomm*. Actually the rfcomm device node will created by the moto-sync plugin via the bluez DBUS API, but cannot access the device node by default.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222555 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com AssignedTo|seife@novell.com |lnussel@novell.com ------- Comment #1 from lnussel@novell.com 2006-11-20 02:08 MST ------- What kind of device is that? Is it a serial device where you can use AT commands that can make the phone dial numbers? Anyways, please attach the output of lshal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222555 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dgollub@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222555 ------- Comment #2 from seife@novell.com 2006-11-20 09:17 MST ------- (In reply to comment #1)
What kind of device is that? Is it a serial device where you can use AT commands that can make the phone dial numbers?
yes, it is a serial-port via bluetooth. You can usually dial out there.
Anyways, please attach the output of lshal.
I doubt it is useful, since the /dev/rfcomm* is a "virtual" device that builds on the bluetooth adapter. In other words: seife@strolchi:~> rfcomm rfcomm0: 00:12:EE:23:CE:EA channel 1 clean rfcomm1: 00:12:EE:23:CE:EA channel 2 clean seife@strolchi:~> lshal |grep rfcomm seife@strolchi:~> which means: although i have a rfcomm device (2 actually), it does not show up in HAL. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=222555 dgollub@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dgollub@novell.com | Resolution| |INVALID ------- Comment #5 from dgollub@novell.com 2007-01-16 07:36 MST ------- At least for the moto-sync use case we solved the problem. moto-sync is now able to have a direct bluetooth connection with the pybluez wrapper. I hope the bluetooth pairing authentication is security enough to prevent sending "evil" AT+ commands.... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com