From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 3 12:11:58 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 540C61065671 for ; Thu, 3 Apr 2008 12:11:58 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id 0CCBE8FC23 for ; Thu, 3 Apr 2008 12:11:57 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by localhost.localdomain with esmtp (Exim 4.50) id 1Jh34c-0000WU-Lf; Wed, 02 Apr 2008 14:32:18 +0100 Received: from localhost.localdomain ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01872-08; Wed, 2 Apr 2008 14:32:18 +0100 (BST) Received: from [10.32.45.24] (helo=rya-online.net) by localhost.localdomain with smtp (Exim 4.50) id 1Jh34a-0000WP-Cw; Wed, 02 Apr 2008 14:32:18 +0100 Received: (nullmailer pid 1331 invoked by uid 1000); Wed, 02 Apr 2008 13:32:04 -0000 Date: Wed, 2 Apr 2008 14:32:04 +0100 (BST) To: mato In-Reply-To: <47F13FEB.10503@users.sf.net> References: <47DBE7A4.3060006@users.sf.net> <47EF6AA5.60403@users.sf.net> <47F13FEB.10503@users.sf.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1207143124.467349.1017.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost.localdomain); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT issues X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2008 12:11:58 -0000 On Mon, 31 Mar 2008, mato wrote: > However, Windows can manage this as it asks for PIN key when connection > initiation fails. While I don't expect FreeBSD asking for a PIN, it might be > quite useful if it could automatically (upon a connection establishing > failure) throw away its stored link key and recreate it from PIN as Windows > does. btw That would be the wrong thing to do. The stored link key is the 'password' for the remote BDADDR to connect to your services and it is possible on many devices to change the bluetooth device address (BDADDR) You don't want to make it so that a remote attacker can just cause a 'password' reset by pretending to be an authorised device, and this is the reason PINs should not be permanently stored.. iain