summaryrefslogtreecommitdiff
path: root/usr.sbin/btdevctl/btdevctl.c
AgeCommit message (Collapse)Author
2011-08-27static + __deadjoerg
2011-03-20provide more informative error messagesplunky
2009-05-12update to use new sdp(3) and sdp_data(3) APIsplunky
2008-07-21Remove the \n and tabs from the __COPYRIGHT() strings.lukem
Tweak to use a consistent format.
2007-11-19use optarg instead of mode when reporting failure - mode is uninitialisedplunky
2007-08-17Attempt at fixing build failures after proplib was converted to bool:pavel
FALSE -> false, TRUE -> true, boolean_t -> bool, int -> bool when appropriate, include stdbool.h . proplib.h no longer provides boolean_t, so it is necessary to change to bool. From Tom Spindler (dogcow@).
2007-04-21Add 'service level' security for L2CAP and RFCOMM connections, followingplunky
the Linux (BlueZ) API. - L2CAP or RFCOMM connections can require the baseband radio link mode be any of: authenticated (devices are paired) encrypted (implies authentication) secured (encryption, plus generate new link key) - for sockets, the mode is set using setsockopt(2) and the socket connection will be aborted if the mode change fails. - mode settings will be applied during connection establishment, and for safety, we enter a wait state and will only proceed when the mode settings are successfuly set. - It is possible to change the mode on already open connections, but not possible to guarantee that data already queued (from either end) will not be delivered. (this is a feature, not a bug) - bthidev(4) and rfcomm_sppd(1) support "auth", "encrypt" and "secure" options - btdevctl(8) by default enables "auth" for HIDs, and "encrypt" for keyboards (which are required to support it)
2006-09-11also include service name in dictionary being sent to kernel.plunky
(this is not used just yet, but it might be in the future and it will be easier if we dont have to provide code to handle its absence)
2006-09-10update to bluetooth device attachment:plunky
remove pseudo-device btdev(4) and inherent limitations add bthub(4) which autoconfigures at bluetooth controllers as they are enabled. bluetooth devices now attach here. btdevctl(8) and its cache is updated to handle new semantics etc/rc.d/btdevctl is updated to configure devices from a list in /etc/bluetooth/btdevctl.conf
2006-08-13rename btcontrol(8) as btdevctl(8) to make it fit with the NetBSD namingplunky
scheme for control programs. This fixes pr 34051.