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

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