Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bthcid(8) [netbsd man page]

BTHCID(8)						    BSD System Manager's Manual 						 BTHCID(8)

bthcid -- Bluetooth Link Key/PIN Code Manager SYNOPSIS
bthcid [-fn] [-d device] [-m mode] [-s socket_name] bthcid [-h] DESCRIPTION
The bthcid daemon handles Link Key and PIN code requests for Bluetooth devices. It opens a raw HCI socket and listens for the following HCI events. Link_Key_Request bthcid scans the /var/db/bthcid.keys file for a cached link key matching the remote device BD_ADDR and, if found, the Link_Key_Request_Reply will be sent back to the device, otherwise the Link_Key_Request_Negative_Reply will be sent. Link_Key_Notification When a new link key is created by the device, it will be cached for future use in the /var/db/bthcid.keys link keys file, which will be created if it does not already exist. PIN_Code_Request The bthcid daemon checks its PIN cache for a matching remote device entry. If no PIN is found, the bthcid daemon will send a message to any PIN clients that have registered, with the device details and a timeout value. When no clients are available or the timeout has expired, bthcid will send a PIN_Code_Request_Negative_Reply back to the device. When a PIN is found, or if a client responds within the timeout period, a PIN_Code_Request_Reply will be sent back to the device. PINs received from clients will be cached for 5 minutes until used, and may be added to the cache prior to pairing with the btpin(1) utility. Some of the functionality of bthcid can be handled by the Bluetooth controller directly, and cached Link Keys may be examined, deleted or moved to device storage using the btkey(1) program. The command line options are as follows: -d device Specify the local Bluetooth device address. The default is BDADDR_ANY. -f Run in foreground (do not detach). -h Display usage message and exit. -m Specify the file mode access bits for the PIN client socket. The default is to allow readwrite access to user and group (0660). -n Do not listen for PIN clients. -s socket_name Specify the socket name to listen on for PIN clients. The default path is /var/run/bthcid. FILES
/var/db/bthcid.keys /var/run/bthcid /var/run/ SEE ALSO
btkey(1), btpin(1), bluetooth(4), btconfig(8) HISTORY
The bthcid daemon first appeared in FreeBSD 5.3 as hcsecd. It was ported to NetBSD 4.0 with its present name and extended to support PIN clients by Iain Hibbert under the sponsorship of Itronix, Inc. AUTHORS
Maksim Yevmenkin <> Iain Hibbert BSD
September 29, 2006 BSD

Check Out this Related Man Page

HCSECD.CONF(5)						      BSD File Formats Manual						    HCSECD.CONF(5)

hcsecd.conf -- hcsecd(8) configuration file DESCRIPTION
The hcsecd.conf file is the configuration file for the hcsecd(8) Bluetooth link keys/PIN codes management daemon. The hcsecd.conf file is a free-form ASCII text file. It is parsed by the recursive-descent parser built into hcsecd(8). The file may con- tain extra tabs and newlines for formatting purposes. Keywords in the file are case-sensitive. Comments may be placed anywhere within the file (except within quotes). Comments begin with the '#' character and end at the end of the line. FILE FORMAT
The hcsecd.conf file consists of a list of device entries. Each device entry defines a link key or PIN code for a remote Bluetooth device. Each remote Bluetooth device is identified by its unique BD_ADDR. The device entry device { option argument; [option argument;] } The following section describes all supported options and arguments. bdaddr BD_ADDR Specify remote device BD_ADDR for the entry. name device_name Specify user friendly name for the entry. Name is a string in straight double quotes. key link_key Specify link key for the entry. Link key is hexadecimal string up to 32 characters in length starting with '0x'. key nokey Specify no link key for the entry. pin PIN_code Specify PIN code for the entry. PIN code is a string up to 16 characters in length in straight double quotes. pin nopin Specify no PIN code for the entry. EXAMPLES
A sample hcsecd.conf file: # Default entry is applied if no better match found # It MUST have 00:00:00:00:00:00 as bdaddr device { bdaddr 00:00:00:00:00:00; name "Default entry"; key nokey; pin nopin; } # Ericsson T68 phone device { bdaddr 00:80:37:5e:4d:d4; name "Ericsson T68 phone"; key nokey; pin "0000"; # PIN code } # Dummy device device { bdaddr 00:11:22:33:44:55; name "Dummy"; key 0x00112233445566778899aabbccddeeff; # 16 bytes key pin nopin; } SEE ALSO
hcsecd(8) AUTHORS
Maksim Yevmenkin <> BSD
May 26, 2003 BSD
Man Page