From owner-freebsd-bluetooth@freebsd.org Fri Oct 2 18:40:25 2015 Return-Path: Delivered-To: freebsd-bluetooth@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9AC2A0E6FB for ; Fri, 2 Oct 2015 18:40:25 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AD261A62 for ; Fri, 2 Oct 2015 18:40:24 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 48364 invoked from network); 2 Oct 2015 18:40:21 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 2 Oct 2015 18:40:21 -0000 Subject: Re: first shot at user friendly bluetooth-config script To: Maksim Yevmenkin References: <56072A53.4010005@erdgeist.org> <5608199F.9020105@erdgeist.org> Cc: "freebsd-bluetooth@freebsd.org" From: Dirk Engling X-Enigmail-Draft-Status: N1110 Message-ID: <560ECF93.4060804@erdgeist.org> Date: Fri, 2 Oct 2015 20:40:19 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2015 18:40:26 -0000 On 30.09.15 23:30, Maksim Yevmenkin wrote: > there is /usr.bin/bluetooth and /usr.sbin/bluetooth, so somewhere under > one of those would be a good place, imo. Added in phabricator under usr.bin/bluetooth for now. https://reviews.freebsd.org/D3778 > right. so, if pc-bsd is your goal, and, you can rely on graphical > interface, then i would suggest to basically No, PC-BSD is not my goal. Actually I am not using it. But watching my friend struggle gave me the idea. There's many other use cases where you wouldn't even assume a GUI in the first place, like pairing a mobile phone for dialup. > 2) teach hcsecd to run external process to obtain a pin (with timeout) It already knows this, it's in its config file. The missing part is to provide feedback if the PIN or the nopin option was rejected by hcsecd. That could be done with an entry in hcsecd.keys, maybe with a time stamp of the last negative command, so that you can compare it to the hcsecd.conf's time stamp. erdgeist