From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 26 08:14:39 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71C9C16A41F for ; Mon, 26 Sep 2005 08:14:39 +0000 (GMT) (envelope-from vances@feeble.motivity.ca) Received: from frogman.motivity.ca (frogman.motivity.ca [64.235.96.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 120E543D4C for ; Mon, 26 Sep 2005 08:14:38 +0000 (GMT) (envelope-from vances@feeble.motivity.ca) Received: from feeble.motivity.ca ([198.96.119.76]) by frogman.motivity.ca (8.12.11/8.12.11) with ESMTP id j8Q8EaiS077405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 26 Sep 2005 04:14:37 -0400 (EDT) (envelope-from vances@feeble.motivity.ca) Received: (from vances@localhost) by feeble.motivity.ca (8.13.3/8.13.3/Submit) id j8Q8ERCR001883; Mon, 26 Sep 2005 04:14:27 -0400 (EDT) (envelope-from vances) Date: Mon, 26 Sep 2005 04:14:27 -0400 From: Vance Shipley To: Maksim Yevmenkin Message-ID: <20050926081427.GA597@feeble.motivity.ca> References: <20050925225336.GA2110@feeble.motivity.ca> <43374D24.7010701@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43374D24.7010701@savvis.net> User-Agent: Mutt/1.4.2.1i Organization: Motivity Telecom Inc. Cc: freebsd-bluetooth@freebsd.org Subject: Re: Is encryption supported? 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: Mon, 26 Sep 2005 08:14:39 -0000 On Sun, Sep 25, 2005 at 06:21:40PM -0700, Maksim Yevmenkin wrote: } } if i'm not mistaken, the specification says that encryption will be } enabled if connection authentication enabled as well, so you need } } # hccontrol -n ubt0hci write_authentication_enable 1 } # hccontrol -n ubt0hci write_encryption_mode 1 Max, Thanks, that did the trick. } link authentication and encryption is really silly (kinda like WEP). if } you really want encryption you should not use bluetooth. i'm not even } sure why your application insists on it. bluetooth connections usually The author of gnubox put a dialog up to choose whether or not to enable encryption however on the Nokia 6620 port of the code it didn't work and it only gave you an "Ok" choice. This was a known bug. Having pointed out on his online forum that this otherwise innocuous bug was causing me a problem with FreeBSD a new version was made available to me just now which now correctly provides a "Yes" and "No" choice and works as expected. So now I can have it either way. I like it when a plan comes together. :) -Vance