Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hcsecd(8) [freebsd man page]

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

hcsecd -- control link keys and PIN codes for Bluetooth devices SYNOPSIS
hcsecd [-dh] -f configfile DESCRIPTION
The hcsecd daemon controls link keys and PIN codes for Bluetooth devices. It opens a raw HCI socket and listens for Link_Key_Request, PIN_Code_Request and Link_Key_Notification HCI events. Once a Link_Key_Request or PIN_Code_Request HCI event is received, the daemon scans the configuration file for a matching entry. The remote device BD_ADDR is used as a key. If no matching entry was found, the default entry will be used. If no default entry was found then it is assumed that no link key and no PIN code exists. For any given entry, the link key takes precedence over the PIN code. If a link key was not specified, the device must generate the link key from the PIN code. If an entry was found and the link key (or PIN code) exists, the Link_Key_Request_Reply (or PIN_Code_Request_Reply) command will be sent back to the device. Otherwise, the Link_Key_Request_Negative_Reply (or PIN_Code_Request_Negative_Reply) command will be sent back to the device. The hcsecd daemon also handles HCI Link_Key_Notification events and caches link keys created from the PIN codes in memory. To preserve link keys between restarts the hcsecd daemon dumps link keys for all entries in the /var/db/hcsecd.keys link keys file. If it exists, the link keys file gets processed by the hcsecd daemon after it processes its main configuration file. The link keys file gets written every time the hcsecd daemon shuts down gracefully. It is possible to force the hcsecd daemon to re-read its main configuration file and dump the link keys file by sending the HUP signal to the hcsecd process. The user is expected to not modify the link keys file by hand. The command line options are as follows: -d Do not detach from the controlling terminal. -f configfile Specify the name of the configuration file. The default is /etc/bluetooth/hcsecd.conf. -h Display usage message and exit. FILES
/etc/bluetooth/hcsecd.conf /var/db/hcsecd.keys /var/run/ SEE ALSO
ng_btsocket(4), ng_hci(4), hcsecd.conf(5), hccontrol(8), hcseriald(8) AUTHORS
Maksim Yevmenkin <> BUGS
Currently there is no way to select the link key or the PIN code based on which local device received the request. Everything is based on the remote device BD_ADDR. An interface for external helpers to obtain link keys and PIN codes is missing. BSD
November 16, 2002 BSD

Check Out this Related 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
Man Page