*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> hcsecd (8)              



NAME    [Toc]    [Back]

     hcsecd -- control link keys and PIN codes for Bluetooth devices

SYNOPSIS    [Toc]    [Back]

     hcsecd [-dh] -f configfile

DESCRIPTION    [Toc]    [Back]

     The hcsecd daemon controls link keys and PIN codes for Bluetooth devices.
     It opens raw HCI socket and listens for the Link_Key_Request,
     PIN_Code_Request and Link_Key_Notification HCI events.

     Once Link_Key_Request or PIN_Code_Request HCI event is received, the daemon
 will scan configuration file for 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, link key
     takes precedence over PIN code.  If link key was not specified, it means
     device must generate link key from PIN code.  If entry was found and the
     link key (or PIN code) exists then 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 event and caches
     link keys created from the PIN codes in the 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 exists, the link keys file
     gets processed by hcsecd daemon after it processes its main configuration
     file.  The link keys file gets written every time hcsecd daemon is gracefully
 shutdown.  It is possible to force hcsecd daemon to re-read its
     main configuration file and dump link keys file by sending HUP signal to
     the hcsecd process.  User is not expected to modify link keys file by

     The command line options are as follows:

     -d      Do not detach from the controlling terminal.

     -f configfile
	     Specify name of the configuration file.  The default is

     -h      Display usage message and exit.

BUGS    [Toc]    [Back]

     Currently there is no way to select link key or PIN code based on which
     local device received the request.  Everything is based on remote device
     BD_ADDR.  Also might implement interface for external helpers to obtain
     link keys and PIN codes.

FILES    [Toc]    [Back]


SEE ALSO    [Toc]    [Back]

     ng_btsocket(4), ng_hci(4), hcsecd.conf(5), hccontrol(8), hcseriald(8)

AUTHORS    [Toc]    [Back]

     Maksim Yevmenkin <m_evmenkin@yahoo.com>

FreeBSD 5.2.1		       November 16, 2002		 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
ng_l2cap FreeBSD Netgraph node type that implements Bluetooth Logical Link Control and Adaptation Protocol (L2CAP)
hcseriald FreeBSD supervise serial Bluetooth devices
ng_ubt FreeBSD Netgraph node type that is also a driver for Bluetooth USB devices
ubtbcmfw FreeBSD Firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices
bcmfw FreeBSD firmware download utility for Broadcom BCM2033 chip based Bluetooth USB devices
udsbr OpenBSD D-Link DSB-R100 USB radio devices driver
ioctl Tru64 Control devices
losetup Linux set up and control loop devices
gpioctl OpenBSD control GPIO devices
iopctl OpenBSD a program to control IOP devices
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service