public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: shanevolpe@gmail.com
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] devices always connect with out asking for PIN even with pairing enabled!
Date: Thu, 6 Sep 2007 16:06:04 -0400	[thread overview]
Message-ID: <8c7950360709061306w39a081f1od1c372dafabc5072@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4507 bytes --]

I have two embedded Linux devices that I'm running a network between using
PAN.  I have decided that I would like to enable pairing and eventually
encryption for security reasons.
Here is what I have done I'm starting pand master with the following:
pand --listen --master --role  NAP
and the slave with
pand --connect 00:A0:96:18:69:D8 --persist
were 00:A0:96:18:69:D8 is the masters address.

Below are the hci.conf files for both my master and slave device..

I would expect that when I try to connect with out a passkey-agent running
(on the slave) I would not be able to connect but that is not the case.  The
slave connects to the master every time.

I also tried "hciconfig hci0 delkey _bt_address_"
on both the slave and master where _bt_address_ was the address of the other
device.
What am I doing incorrect?
Regards,
Shane

************Master Unit hci.conf file*********************
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.4 2004/04/29 20:14:21 holtmann Exp $
#

# 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 auto;

        # 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 /bin/bluepin;
        passkey "shane";
        # D-Bus PIN helper
        # dbus_pin_helper;
}

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

        # Local device class
        class 0x120112;

        # 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,master;
        #
        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 hold,sniff;
        #
        lp rswitch,hold,sniff,park;

        # Authentication and Encryption
        #auth enable;
        #encrypt enable;
}

****************Slave Unit hci.conf file******************
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.4 2004/04/29 20:14:21 holtmann Exp $
#

# 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 auto;

        # 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 /bin/bluepin;
        # D-Bus PIN helper
        # dbus_pin_helper;
}

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

        # Local device class
        class 0x120112;

        # 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,master;
        #
        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 hold,sniff;
        #
        lp rswitch,hold,sniff,park;

        # Authentication and Encryption
        #auth enable;
        #encrypt enable;
}

[-- Attachment #1.2: Type: text/html, Size: 9137 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-09-06 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 20:06 shanevolpe [this message]
2007-09-10 19:10 ` [Bluez-users] devices always connect with out asking for PIN even with pairing enabled! Marcel Holtmann
2007-09-10 19:56   ` shanevolpe
2007-09-10 20:56     ` Marcel Holtmann
2007-09-11 12:12       ` shanevolpe
2007-09-11 15:15         ` Marcel Holtmann
2007-09-11 16:00           ` Marcus C. Gottwald

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=8c7950360709061306w39a081f1od1c372dafabc5072@mail.gmail.com \
    --to=shanevolpe@gmail.com \
    --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