From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 27 18:59:34 2009 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 77B5C106568B for ; Sun, 27 Dec 2009 18:59:34 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp6.freeserve.com [193.252.22.191]) by mx1.freebsd.org (Postfix) with ESMTP id 11FFF8FC17 for ; Sun, 27 Dec 2009 18:59:33 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3611.me.freeserve.com (SMTP Server) with ESMTP id C96D9700008B; Sun, 27 Dec 2009 19:59:32 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3611.me.freeserve.com (SMTP Server) with ESMTP id B8E00700008F; Sun, 27 Dec 2009 19:59:32 +0100 (CET) Received: from rya-online.net (unknown [89.194.194.54]) by mwinf3611.me.freeserve.com (SMTP Server) with SMTP id A4BAB700008B; Sun, 27 Dec 2009 19:59:31 +0100 (CET) X-ME-UUID: 20091227185931674.A4BAB700008B@mwinf3611.me.freeserve.com Received: (nullmailer pid 685 invoked by uid 1000); Sun, 27 Dec 2009 18:59:31 -0000 Date: Sun, 27 Dec 2009 18:59:31 +0000 (GMT) To: "M\. Warner Losh" In-Reply-To: <20091227.111711.287595822663154592.imp@bsdimp.com> References: <20091227.004954.119882392218644339.imp@bsdimp.com> <20091227.005757.195066307562707339.imp@bsdimp.com> <1261935364.501662.751.nullmailer@galant.ukfsn.org> <20091227.111711.287595822663154592.imp@bsdimp.com> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1261940371.044739.879.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: Keyboard - how? 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: Sun, 27 Dec 2009 18:59:34 -0000 On Sun, 27 Dec 2009, M. Warner Losh wrote: > In message: <1261935364.501662.751.nullmailer@galant.ukfsn.org> > Iain Hibbert writes: > : - IMO the PIN should be ephemeral and use-once so when you are paired you > : should remove it from the config file or at least comment it out > > The whole pairing thing is kind of ugly atm in FreeBSD. I used big > hammers, I think, to make it work. In other OSes, I just see what is > discoverable, click a couple of times, maybe enter a PIN and I then > promptly forget about it until I have to 'unpair'. I have had complaints about it in NetBSD too and while I think I improved on Max's start it still needs further work and should be graphical. I'm not sure about the whole dbus thing that BlueZ is moving to now though it does work well as you say with the GNOME application. I thought about working something lightweight up with (eg) tcl/tk but haven't got around to it yet.. > : > Now, I guess the next step would be to find the bt mouse I have and > : > try to get it going as well... > : > : that is probably fixed pin 0000 if not in the documentation > > Yes, it is :) The default is to no pin, so it wasn't authenticating. Some devices that I noticed will only enforce the auth on making or accepting the connection. Even the Linux stack used to do this (on the accept path only) but I think they fixed it now. > : > This is my second favorite keyboard ever. > : > : How is the keypress feel? I've not had a go on one of those, but I have > : an original apple bluetooth keyboard (white with clear undershell, full > : sized with num keypad) that works well though a smaller one might be > : interesting. > > It is ok. Not as good as the happy hacking keyboard, but certainly > nice enough to use. Better than most to my feel, but ymmv. I will have to take a trip to the Apple store as it looks a bit rubbery, I want to play with a magic mouse too and I saw that they had some of them last week. (it will not be easy to support properly, I have seen some connection logs and it does some private internal feature back and forth conversation first - we thought that probably enables the touch pad feature which might not be too hard to do, but the driver must then interpret all the swipes itself) > btw, is there some way I can easily list the paired devices? 'easily' not really, but /var/db/hcsecd.keys should contain keys for all paired devices. Actually, there can be more keys stored in the device itself (if you paired with another OS that might happen or you can do it manually). I think you can check/change/remove those with hccontrol but must edit the hcsecd.keys file manually. iain