Linux bluetooth development
 help / color / mirror / Atom feed
From: "Rolf S. Dubitzky " <Dubitzky@physi.uni-heidelberg.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: hcid crashing on pin_code_request
Date: Mon, 14 Nov 2005 19:13:47 +0100	[thread overview]
Message-ID: <200511141913.48954.Dubitzky@physi.uni-heidelberg.de> (raw)
In-Reply-To: <200511141705.51539.Dubitzky@physi.uni-heidelberg.de>

> I fixed this problem by including:
>         auth disable;
>         encrypt disable;
> in /etc/bluetooth/hcid.config. I hope ot works for you too :)

I had that already... :-(

-R

--------------

# cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#

# HCId options
options {
        # Automatically initialize new devices
        autoinit yes;

        # Security Manager mode
        #   none - Security manager disabled
        #   auto - Use local PIN for incoming connections
        #   user - Always ask user for a PIN
        #
        security user;

        # Pairing mode
        #   none  - Pairing disabled
        #   multi - Allow pairing with already paired devices
        #   once  - Pair once and deny successive attempts
        pairing multi;

        # PIN helper
        pin_helper /etc/bluetooth/pinhelper;

        # D-Bus PIN helper
        #dbus_pin_helper;
}

# Default settings for HCI devices
device {
        # Local device name
        #   %d - device id
        #   %h - host name
        name "BlueZ (%d)";

        # Local device class
        class 0x3e0100;

        # Default packet type
        #pkt_type DH1,DM1,HV1;

        # Inquiry and Page scan
        iscan enable; pscan enable;

        # Default link mode
        #   none   - no specific policy
        #   accept - always accept incoming connections
        #   master - become master on incoming connections,
        #            deny role switch on outgoing connections
        lm accept;

        # Default link policy
        #   none    - no specific policy
        #   rswitch - allow role switch
        #   hold    - allow hold mode
        #   sniff   - allow sniff mode
        #   park    - allow park mode
        lp rswitch,hold,sniff,park;

        # Authentication and Encryption (Security Mode 3)
        auth disable;
        encrypt disable;
}


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2005-11-14 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 13:52 [Bluez-users] hcid crashing on pin_code_request Rolf S. Dubitzky 
2005-11-14 16:05 ` [Bluez-users] " Rolf S. Dubitzky 
2005-11-14 16:38   ` jimmi
2005-11-14 18:13   ` Rolf S. Dubitzky  [this message]
2005-11-15  9:22     ` Rolf S. Dubitzky 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511141913.48954.Dubitzky@physi.uni-heidelberg.de \
    --to=dubitzky@physi.uni-heidelberg.de \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox