![](https://seccdn.libravatar.org/avatar/af22e20b6884acbc89be6d7736c43e92.jpg?s=120&d=mm&r=g)
Hello community, here is the log from the commit of package bluez-utils checked in at Thu Nov 16 18:44:27 CET 2006. -------- --- bluez-utils/bluez-utils.changes 2006-11-15 15:20:45.000000000 +0100 +++ /mounts/work_src_done/STABLE/bluez-utils/bluez-utils.changes 2006-11-16 15:06:01.000000000 +0100 @@ -1,0 +2,5 @@ +Thu Nov 16 15:05:30 CET 2006 - seife@suse.de + +- update the README.SUSE (bug #221601) + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ bluez-utils.spec ++++++ --- /var/tmp/diff_new_pack.oU2lKk/_old 2006-11-16 18:43:52.000000000 +0100 +++ /var/tmp/diff_new_pack.oU2lKk/_new 2006-11-16 18:43:52.000000000 +0100 @@ -14,7 +14,7 @@ BuildRequires: alsa-devel bluez-libs cups dbus-1-devel fuse-devel libusb openobex-devel pkgconfig resmgr xorg-x11-devel URL: http://bluez.sourceforge.net Version: 3.7 -Release: 23 +Release: 24 Summary: Bluetooth Daemons and Utilities License: GNU General Public License (GPL) PreReq: %fillup_prereq %insserv_prereq @@ -261,6 +261,8 @@ %doc %{_defaultdocdir}/bluez-test %changelog -n bluez-utils +* Thu Nov 16 2006 - seife@suse.de +- update the README.SUSE (bug #221601) * Wed Nov 15 2006 - dgollub@suse.de - bumped bluez-utils version in README.SUSE * Sat Nov 11 2006 - dgollub@suse.de ++++++ README.SUSE ++++++ --- bluez-utils/README.SUSE 2006-11-15 15:19:32.000000000 +0100 +++ /mounts/work_src_done/STABLE/bluez-utils/README.SUSE 2006-11-16 14:23:13.000000000 +0100 @@ -1,15 +1,23 @@ These latest packages are updates to version 3.7, which brings some different configuration options. -WARNING: the YaST2 bluetooth module will not function correctly with - these packages, especially the PIN and the security settings - will not work out of the box. +The whole process of providing a PIN for generating a link key for the +bluetooth connection has changed. In the old version (2.x), a helper +program was called that provided the PIN on its standard output. In +SUSE, this taks was usually achieved by kbluetoothd. The standard pin +helper also was able to read a PIN from /etc/bluetooth/pin. This is +completely reworked now. +Now a process called a "passkey agent" has to register on the D-Bus +and provide the PIN upon request. Don't worry, this is easier than +it sounds. You have to either: - - set your pin in /etc/bluetooth/hcid.conf: + - set your PIN in /etc/bluetooth/hcid.conf: security auto; passkey "your_PIN"; - This will only work for incoming connections. + This will only work for incoming connections and is not very useful + because of that limitation. This is also the PIN set by the YaST2 + bluetooth module. - set security to "user" in hcid.conf: security user; and then start passkey-agent before trying to pair your @@ -19,12 +27,12 @@ Passkey-agent won't exit once the device is paired, you have to abort it with CTRL-C. -This is a temporary solution, until kbluetoothd has support for DBUS -and the YaST2 bluetooth module has been updated. +Or you just start kbluetoothd (KDE, package kdebluetooth) or +bluetooth-applet (GNOME, package bluez-gnome) which both contain a nice +graphical passkey agent. -If you used the YaST2 bluetooth module or updated from an older version, -you have to remove the "auth" and "encrypt" lines from hcid.conf, -otherwise it probably won't work. +If you updated from an older version, you have to remove the "auth" and +"encrypt" lines from hcid.conf, otherwise it probably won't work. Another change is that per default, the adapter gets invisible after 3 minutes. You can set this value via the BlueZ-DBus-interface. If set ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Remember to have fun... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-commit+help@opensuse.org
participants (1)
-
root@suse.de