HCSECD.CONF(5) BSD File Formats Manual HCSECD.CONF(5)NAME
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 <m_evmenkin@yahoo.com>
BSD May 26, 2003 BSD
Check Out this Related Man Page
HCSECD(8) BSD System Manager's Manual HCSECD(8)NAME
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/hcsecd.pid
SEE ALSO ng_btsocket(4), ng_hci(4), hcsecd.conf(5), hccontrol(8), hcseriald(8)AUTHORS
Maksim Yevmenkin <m_evmenkin@yahoo.com>
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