btpin(1) [netbsd man page]
BTPIN(1) BSD General Commands Manual BTPIN(1) NAME
btpin -- Bluetooth PIN utility SYNOPSIS
btpin [-P] [-d device] [-s path] {-p pin | -r [-l len]} -a address DESCRIPTION
The btpin utility is used to register a temporary PIN with the bthcid(8) daemon for the purposes of pairing Bluetooth devices. The PIN will be valid for 5 minutes or until used, whichever comes first. The options are as follows: -a address Specify the remote device address. The address can be specified as BD_ADDR or a name. If a name was specified, the btpin utility attempts to resolve the name via bt_gethostbyname(3). -d device Specify the local device address. The device can be specified by BD_ADDR or device name. See btconfig(8) for a list of devices available. If no device is specified, the PIN will be valid for any local device. -l len Specify length of PIN to generate, where 1 <= len <= 16. -P Pair with remote device. btpin will attempt to open an authenticated L2CAP connection to the Service Discovery Service on the remote device, to force immediate pairing. -p pin The PIN to register. The PIN may be up to 16 bytes in length. -r Generate a random PIN, the default length is 4 bytes. -s path Specify path to the control socket. The default path is /var/run/bthcid. EXIT STATUS
The btpin utility exits 0 on success, and >0 if an error occurs. FILES
/var/run/bthcid SEE ALSO
btkey(1), btconfig(8), bthcid(8) AUTHORS
Iain Hibbert for Itronix, Inc BSD
May 16, 2009 BSD
Check Out this Related Man Page
BTHCID(8) BSD System Manager's Manual BTHCID(8) NAME
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/bthcid.pid 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 <m_evmenkin@yahoo.com> Iain Hibbert BSD
September 29, 2006 BSD