[Bug 217079] New: YaST2 Bluetooth should set proper device class (computer form factor)
https://bugzilla.novell.com/show_bug.cgi?id=217079 Summary: YaST2 Bluetooth should set proper device class (computer form factor) Product: openSUSE 10.2 Version: Beta 1 Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sbrabec@novell.com QAContact: jsrain@novell.com According to /etc/bluetooth/hcid.conf comments, YaST sets device class to "Computer". It would be nice to consider computer form factor and set properly to "Computer Desktop" or "Computer Laptop" (easy to detect from hal /org/freedesktop/Hal/devices/computer system.formfactor or smbios.chassis.type) and maybe "Computer Server" (hard to discriminate between desktop and server, but SLES can set it). -- 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=217079 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.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=217079 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@novell.com AssignedTo|lslezak@novell.com |seife@novell.com Component|YaST2 |Mobile Devices Summary|YaST2 Bluetooth should set |bluetooth - the default computer class should be |proper device class |more specific |(computer form factor) | ------- Comment #1 from lslezak@novell.com 2006-11-06 10:32 MST ------- "Computer" is the default value in /etc/bluetooth/hcid.conf, yast changes it only on user request (in the respective dialog) . I think the only way to change the default is a postinstall script in bluez-utils package. -- 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=217079 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgollub@novell.com, security-team@suse.de ------- Comment #2 from seife@novell.com 2006-11-06 11:20 MST ------- And we'd need to make sure that hal is running and has all the databases to determine the formfactor. Is it worth the pain? Next would be the question if this is confidential information and may be disclosed without asking the user (cc'ing security) -- 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=217079 ------- Comment #3 from thomas@novell.com 2006-11-07 07:18 MST ------- It may ease attacks because the attackers will know what packages could be used. impact is - of course - very low (BT is short range, port scanning reveals services nevertheles, to be attacked client apps can be determined via other ways too (i.e. email header for MUA)). -- 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=217079 ------- Comment #4 from seife@novell.com 2006-11-07 07:24 MST ------- Ok, so the security problem is not a real one (somebody paranoid about that should pull its BT device out anyway ;-) Thanks for commenting. I will remove security-team from Cc of this bug, i guess you get enough mail already. -- 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=217079 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|security-team@suse.de | Status|NEW |NEEDINFO Info Provider| |sbrabec@novell.com ------- Comment #5 from seife@novell.com 2006-11-07 07:27 MST ------- Ok, so what is the use case? I don't want to modify the config file in postinst because i'd need to make sure that HAL is running correctly etc., but if you give me a nice patch / script to do that, i might reconsider :-) Another option would be, to let hcid query HAL by itself or let the init script set this options via dbus to the HAL queried defaults (but it needs to be configurable, since i might want to run a "server" on a machine that is actually a notebook :-) First tell me about the use case, though. -- 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=217079 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sbrabec@novell.com | ------- Comment #6 from sbrabec@novell.com 2006-11-13 08:21 MST ------- Maybe ask hal only if "class" in /etc/bluetooth/hcid.conf is configured to do so, e. g. by setting device class bits to zeros. And zeros can be default value. I can also imagine, that the form factor is set during the first start of the init script. -- 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=217079 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |LATER ------- Comment #7 from seife@novell.com 2006-11-13 09:46 MST ------- I still don't see any useful application for that :-) Anyway, we can only do this once we can set those settings via Dbus since changing the config file automagically is not a good idea IMO. So let's wait what the great dbusification of bluez will bring us. -- 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=217079 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=217079#c10 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #10 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:19:18 MDT --- mass reopening all 10.2 LATER+REMIND bugs. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=217079 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=217079#c11 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #11 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:23:31 MDT --- close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com