slackware-current/source/n/bluez-utils
Patrick J Volkerding 5a12e7c134 Slackware 13.0
Wed Aug 26 10:00:38 CDT 2009
Slackware 13.0 x86_64 is released as stable!  Thanks to everyone who
helped make this release possible -- see the RELEASE_NOTES for the
credits.  The ISOs are off to the replicator.  This time it will be a
6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD.
We're taking pre-orders now at store.slackware.com.  Please consider
picking up a copy to help support the project.  Once again, thanks to
the entire Slackware community for all the help testing and fixing
things and offering suggestions during this development cycle.
As always, have fun and enjoy!  -P.
2018-05-31 22:41:17 +02:00
..
60-bluetooth.rules Slackware 13.0 2018-05-31 22:41:17 +02:00
add-passkey.c Slackware 13.0 2018-05-31 22:41:17 +02:00
bluetooth.conf Slackware 13.0 2018-05-31 22:41:17 +02:00
bluez-utils.SlackBuild Slackware 13.0 2018-05-31 22:41:17 +02:00
doinst.sh Slackware 13.0 2018-05-31 22:41:17 +02:00
rc.bluetooth Slackware 13.0 2018-05-31 22:41:17 +02:00
rc.bluetooth.conf Slackware 13.0 2018-05-31 22:41:17 +02:00
README.SLACKWARE Slackware 13.0 2018-05-31 22:41:17 +02:00
register-passkeys Slackware 13.0 2018-05-31 22:41:17 +02:00
slack-desc Slackware 13.0 2018-05-31 22:41:17 +02:00

PIN (or passkey) management
---------------------------
since bluez 3.0 the old pin_helper script has been replaced by
the dbus interface.  To add a default passkey for every outgoing
request (e.g. the old /etc/bluetooth/pin file) drop it into
/etc/bluetooth/passkeys/default. (e.g. echo -n "1234" >
/etc/bluetooth/passkeys/default )
To add a passkey for a specific outgoing connection replace default
with the device's address. ( /etc/bluetooth/passkeys/aa:bb:cc:dd:ee:ff
will contain passkey for aa:bb:cc:dd:ee:ff ).
After adding a passkey you should restart bluetooth with

/etc/init.d/bluetooth restart

and the new passkeys will be registered.


(This behaviour has been copied from Debian)