FreeBSD Bugzilla – Attachment 195403 Details for
Bug 229997
Bluetooth mouse doesn't work on 12: mode_change: ubt0hci - failed to change mode, status=32
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
hcsecd.conf
hcsecd.conf (text/plain), 1.43 KB, created by
Yuri Victorovich
on 2018-07-24 00:22:05 UTC
(
hide
)
Description:
hcsecd.conf
Filename:
MIME Type:
Creator:
Yuri Victorovich
Created:
2018-07-24 00:22:05 UTC
Size:
1.43 KB
patch
obsolete
># $Id: hcsecd.conf,v 1.1 2003/05/26 22:50:47 max Exp $ ># $FreeBSD: head/etc/bluetooth/hcsecd.conf 158726 2006-05-18 17:53:49Z emax $ ># ># HCI security daemon configuration file ># ># Format: ># ># device { ># option value ; ># } ># ># Possible options and values ># ># Options Values ># ---------------------------------- ># bdaddr xx:xx:xx:xx:xx:xx ; - remote device BD_ADDR ># name "any char" ; - to set user friendly device name ># key 0x11223344 | nokey ; - to set link key for the device ># pin "secret" | nopin ; - to PIN code for the device ># ># Notes: ># ># Currently there is no way to select keys/PIN code based on which ># local device received the request. Everything is based on remote ># device BD_ADDR. ># ># "nokey" means that no link key has been defined and we should ># send Link_Key_Negative_Reply command to the device. ># ># "nopin" means that no PIN code has been defined and we should ># send PIN_Code_Negative_Reply command to the device ># > ># 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; >} > >device { > bdaddr 00:01:02:03:04:05; > name "Dummy"; > key nokey; > pin "0000"; >} > >device { > bdaddr 00:11:22:33:44:55; > name "Dummy"; > key 0x00112233445566778899aabbccddeeff; # 16 bytes key (hex string) > pin nopin; >} > >device { > bdaddr 7c:1e:52:73:7d:e1; > name "MS Mouse"; > key nokey; > pin "0000"; >}
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 229997
:
195402
| 195403 |
195404
|
195405