From owner-freebsd-bluetooth@freebsd.org Sun Sep 27 13:19:53 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 A9A28A0A77A for ; Sun, 27 Sep 2015 13:19:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 445A5321 for ; Sun, 27 Sep 2015 13:19:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by wiclk2 with SMTP id lk2so72956663wic.0 for ; Sun, 27 Sep 2015 06:19:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qT1P7pWYWTXagwO3eD0t1MrItLXvUyHE3sfxOMTaxGM=; b=Sd+GE5xkE++bsRWPVojxqYyHpZHdhA2WjXd9vYGH20vK8VCZQ+/fZH9UybI5TgpBKs 9qlbss+WAVbJ7kboORoMRixdpaplGiAsyMOP+FI3Yd32Jb45QOjiGraPMOP93d5TSpa1 J8apmtSrVQ1tHed22/+Yk++Li0zN04Dz+rlmdVEJe9PKM4sefLKKuWEKorCR+KvH3ISS a3uHZqpky/+jwE8ebFMg857q0Ag0PnZtP2MYMQOViNAOMrP6SehpzkWgI7md/1mwiHjs naHwId6GR7jqfHXR4ps8EFlf9Abxh9SeK4CL7XgSe1ku1LOaj5B6j/R626Ra3gdkl2kB cs5A== MIME-Version: 1.0 X-Received: by 10.194.184.136 with SMTP id eu8mr18596901wjc.151.1443359991282; Sun, 27 Sep 2015 06:19:51 -0700 (PDT) Received: by 10.28.146.132 with HTTP; Sun, 27 Sep 2015 06:19:51 -0700 (PDT) In-Reply-To: <56072A53.4010005@erdgeist.org> References: <56072A53.4010005@erdgeist.org> Date: Sun, 27 Sep 2015 06:19:51 -0700 Message-ID: Subject: Re: first shot at user friendly bluetooth-config script From: Maksim Yevmenkin To: Dirk Engling Cc: "freebsd-bluetooth@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Sun, 27 Sep 2015 13:19:53 -0000 Hello! thank you for your work. can you please put it into review? also, what is the proposed usage scenario? can you please describe it? thanks max On Sat, Sep 26, 2015 at 4:29 PM, Dirk Engling wrote: > Find attached a script that tries to tie together essential parts of the > bluetooth sub-system in a human friendly manner. > > Currently I implemented all the steps necessary to get a hid running, > and helping out the user along the way. Next up I want to implement > setting up everything necessary to get connected using the DUN profile, > if available. > > Still some questions remain about pairing: besides grepping debug.log's > output, is there a reliable way to get pairing status? Looking into > /var/db/hcsecd.keys may give me positive results, but info like whether > a PIN_Code_Negative_Reply has been sent to the device because of a wrong > pin code would be helpful. It would also be helpful to know if the > device never sent a PIN_Code_Request in the first place. And how do you > use hcsecd to actively start pairing? > > The script's style may still be a little concise, but is extensively > documented, I will factor out code blocks into functions later. I am > also trying to make it more usable from a script by adding a quiet mode > that is not interactive and tries to automatically resolve everything by > the info passed on command line. > > Now I wonder, where the code will be heading. Is it likely to go into > the bluetooth framework or should I start writing a port? Do you have > suggestions where the user might be provided additional info on how to > continue, especially if stuff breaks? > > Regards, > > erdgeist > > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to " > freebsd-bluetooth-unsubscribe@freebsd.org" > From owner-freebsd-bluetooth@freebsd.org Sun Sep 27 16:30:30 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 85FBDA0ADAA for ; Sun, 27 Sep 2015 16:30:30 +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 E79B6122 for ; Sun, 27 Sep 2015 16:30:29 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 86664 invoked from network); 27 Sep 2015 16:30:24 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 27 Sep 2015 16:30:24 -0000 Subject: Re: first shot at user friendly bluetooth-config script To: Maksim Yevmenkin References: <56072A53.4010005@erdgeist.org> Cc: "freebsd-bluetooth@freebsd.org" From: Dirk Engling X-Enigmail-Draft-Status: N1110 Message-ID: <5608199F.9020105@erdgeist.org> Date: Sun, 27 Sep 2015 18:30:23 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.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: Sun, 27 Sep 2015 16:30:30 -0000 On 27.09.15 15:19, Maksim Yevmenkin wrote: > thank you for your work. can you please put it into review? Where would I put the script for that regard? Something like /usr/bin? > also, what is the proposed usage scenario? can you please describe > it? As I mentioned earlier, the script is supposed to tie several layers of the bluetooth framework together to guide users with day-to-day tasks like pairing a HID device like a keyboard and a mouse. It is intended to serve both as an interactive script, guiding a novice user through the common pitfalls, dumping pointers to config files and man pages along the way and also as a scriptable back-end to a yet-to-be written GUI (e.g. a config panel in PC-BSD). I think I laid out my motivation for writing it in earlier emails. Having proper documentation on a framework (which FreeBSD clearly lacks) would be a good thing, but making it further less likely to have users shoot themselves in the feet by implementing best practices that will suite the need of 99% of FreeBSD's bluetooth users is even better. In my experience the best framework is worthless if not properly exposed to the end user. And frankly, currently it is not exposed to the end user at all. I consider myself rather fluent in FreeBSD, I am able to understand complex protocols and their C code implementation and yet, standing with my PC-BSD curious buddy on his new shiny development station – combining over 50 years of IT experience – we still struggled for over a day, trying to figure out how the pieces fit together just to pair a freaking mouse ;) Maybe I am taking it into a completely wrong direction and you have a much simpler way to achieve the task that I just have not understood. Regards erdgeist From owner-freebsd-bluetooth@freebsd.org Mon Sep 28 09:16:21 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 1BF8DA0B635 for ; Mon, 28 Sep 2015 09:16:21 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.0x20.net", Issuer "mail.0x20.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D17BC14B4 for ; Mon, 28 Sep 2015 09:16:20 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id D33546DF91B; Mon, 28 Sep 2015 11:16:16 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id t8S9GGIO004934; Mon, 28 Sep 2015 11:16:16 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id t8S9GFJ1004597; Mon, 28 Sep 2015 11:16:15 +0200 (CEST) (envelope-from lars) Date: Mon, 28 Sep 2015 11:16:15 +0200 From: Lars Engels To: Dirk Engling Cc: Maksim Yevmenkin , "freebsd-bluetooth@freebsd.org" Subject: Re: first shot at user friendly bluetooth-config script Message-ID: <20150928091615.GF43663@e-new.0x20.net> References: <56072A53.4010005@erdgeist.org> <5608199F.9020105@erdgeist.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="svZFHVx8/dhPCe52" Content-Disposition: inline In-Reply-To: <5608199F.9020105@erdgeist.org> X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p23 User-Agent: Mutt/1.5.23 (2014-03-12) 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: Mon, 28 Sep 2015 09:16:21 -0000 --svZFHVx8/dhPCe52 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 27, 2015 at 06:30:23PM +0200, Dirk Engling wrote: > On 27.09.15 15:19, Maksim Yevmenkin wrote: >=20 > > thank you for your work. can you please put it into review? >=20 > Where would I put the script for that regard? Something like /usr/bin? No, please add it to FreeBSD's Phabricator system: https://reviews.freebsd.org/ --svZFHVx8/dhPCe52 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJWCQVfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tr6UIAIJ1W9cdMWyDzN/bu94v/aeB js6XdmiItkmF7Cj8baoxVx/KNMvjwBwsn5P0uAlVmRuCc1qKVoCYIFz978fjLjRu 0gDrHAJiWz4SKyfT9LNSqTDk0m+5WYwSYUvVUdo+heMCEn+S+PxL99No/BEKYR9I 3q8DUyUOA3Lpnx1DNfUY2yAAsUDsFYeQKNSMP2IQJy9VZEeO3QxckAAvE/Kh+0hM oeQdKTyXNOnNIn8F3ZhxNsbEh6ErUeuhCwU1uuA+5kL1DwfyX609U01SVE9RgldV qP2DKjMce0Qb+koGinDWLXrttd+g1m3e++JgVmozz2Zo0gSy0DWk8lru9Sxya+4= =PazO -----END PGP SIGNATURE----- --svZFHVx8/dhPCe52-- From owner-freebsd-bluetooth@freebsd.org Wed Sep 30 21:30:53 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 4AF31A0C7CE for ; Wed, 30 Sep 2015 21:30:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3BBD1083 for ; Wed, 30 Sep 2015 21:30:52 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by wiclk2 with SMTP id lk2so5997419wic.0 for ; Wed, 30 Sep 2015 14:30:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XAkU0PfWNtSdYQdllR2wYXJs64jkjyJK+/fIv6GONV4=; b=CIg10/6ARwZtqeyuQhm7L4vn/1bU3v5mwoqsvZr3kiX81v2RA0kM0yWn6BFYaQTcan FqqvgVkoOmpvKsa2aEiws4l7C7AoOxi3A6U46vf50ojtrx6//ZNnWlWQxhXrG3h5uEFL SGmRliwKwk5mTmVG/PzAWL5CHA1TNp/m8kjP988+r27EBzYi6unGvYaS802CJbKFRC/H 1028PRXn3kfx6O8an8rlItouUfinbs2J9Vfh8Jrfmbymu1DTeKJlhv0wf9aEcnucOoaE 3RdrId8U2P55jiRKVAjJ/ITSZne9VtuzfUqsrDZ+3iVw8lAFTEM3NgF+/t5hNRMN5i9C pTSg== MIME-Version: 1.0 X-Received: by 10.180.39.175 with SMTP id q15mr35333020wik.73.1443648650125; Wed, 30 Sep 2015 14:30:50 -0700 (PDT) Received: by 10.28.146.132 with HTTP; Wed, 30 Sep 2015 14:30:50 -0700 (PDT) In-Reply-To: <5608199F.9020105@erdgeist.org> References: <56072A53.4010005@erdgeist.org> <5608199F.9020105@erdgeist.org> Date: Wed, 30 Sep 2015 14:30:50 -0700 Message-ID: Subject: Re: first shot at user friendly bluetooth-config script From: Maksim Yevmenkin To: Dirk Engling Cc: "freebsd-bluetooth@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Wed, 30 Sep 2015 21:30:53 -0000 hello! sorry for the delay, i was afk > > thank you for your work. can you please put it into review? > > Where would I put the script for that regard? Something like /usr/bin? > there is /usr.bin/bluetooth and /usr.sbin/bluetooth, so somewhere under one of those would be a good place, imo. > > also, what is the proposed usage scenario? can you please describe > > it? > > As I mentioned earlier, the script is supposed to tie several layers of > the bluetooth framework together to guide users with day-to-day tasks > like pairing a HID device like a keyboard and a mouse. > ok > It is intended to serve both as an interactive script, guiding a novice > user through the common pitfalls, dumping pointers to config files and > man pages along the way and also as a scriptable back-end to a yet-to-be > written GUI (e.g. a config panel in PC-BSD). > right. so, if pc-bsd is your goal, and, you can rely on graphical interface, then i would suggest to basically 1) completely reimplement hcsecd in terms of graphical ui (you can reuse parts of hcsecd) or 2) teach hcsecd to run external process to obtain a pin (with timeout) > I think I laid out my motivation for writing it in earlier emails. > Having proper documentation on a framework (which FreeBSD clearly lacks) > would be a good thing, but making it further less likely to have users > shoot themselves in the feet by implementing best practices that will > suite the need of 99% of FreeBSD's bluetooth users is even better. > agreed > In my experience the best framework is worthless if not properly exposed > to the end user. And frankly, currently it is not exposed to the end > user at all. I consider myself rather fluent in FreeBSD, I am able to > understand complex protocols and their C code implementation and yet, > standing with my PC-BSD curious buddy on his new shiny development > station =E2=80=93 combining over 50 years of IT experience =E2=80=93 we s= till struggled > for over a day, trying to figure out how the pieces fit together just to > pair a freaking mouse ;) > > Maybe I am taking it into a completely wrong direction and you have a > much simpler way to achieve the task that I just have not understood. > again, when you have graphical ui and can get attention of user it becomes much simplier. so, i think, for pc-bsd case, it would be much better to simply start writing UI controls. thanks max 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 From owner-freebsd-bluetooth@freebsd.org Fri Oct 2 19:28:56 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 D24479D09EF for ; Fri, 2 Oct 2015 19:28:56 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C90D1337 for ; Fri, 2 Oct 2015 19:28:56 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by wicfx3 with SMTP id fx3so46963529wic.1 for ; Fri, 02 Oct 2015 12:28:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WWLlxAAASTPsckRgeqhzV2sP9WCBtdbGqZE6IXy+gv0=; b=ULPES5NM2K6vZT/WBEfxEtmhiNVdkDVJehs48z29J/0uwKp7yFAbDIlqK8MWmsDyx6 R5HFi51RKeyLnuLZ8AFk+ZJxcQ4fVieTuGMcYwcpknOLyYAThkyNEvEVc+jgm90eeUQl EFqYzb5BiD5WkYvHjyRggEul5YtT/H8wVXMOLJI2Zz238rgsKN2aVS1jCXNsQu8rtXOI g7SeDThL0TsrIt7Awe8LIcRHvKVCf2FBVpUpomv32XkQcE7J6EvKScO64wfRTwEIS2wZ 2LKuNe9bBMYzaDYZdaf1u2bff2HeEguYm6iIpjefnnKg4mLongGLeQn2BeV3C1ovOhWQ +Org== MIME-Version: 1.0 X-Received: by 10.180.104.65 with SMTP id gc1mr504015wib.67.1443814133877; Fri, 02 Oct 2015 12:28:53 -0700 (PDT) Received: by 10.28.146.132 with HTTP; Fri, 2 Oct 2015 12:28:53 -0700 (PDT) In-Reply-To: <560ECF93.4060804@erdgeist.org> References: <56072A53.4010005@erdgeist.org> <5608199F.9020105@erdgeist.org> <560ECF93.4060804@erdgeist.org> Date: Fri, 2 Oct 2015 12:28:53 -0700 Message-ID: Subject: Re: first shot at user friendly bluetooth-config script From: Maksim Yevmenkin To: Dirk Engling Cc: "freebsd-bluetooth@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 19:28:56 -0000 > > 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 thanks. i will take a look. > > 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. why not? seems like a perfect case for UI, imo. unless i'm missing something here. > > 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. well, the whole point is not have user to configure it at all, right? who wants to know bd_addr etc. of their bluetooth devices. what (most) users want to see (imo) is that stuff "just works". click on pretty picture of a mouse, enter pin, done. > 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. not sure i understand this. thanks max From owner-freebsd-bluetooth@freebsd.org Sat Oct 3 10:45:35 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 86C29A0F6F7 for ; Sat, 3 Oct 2015 10:45:35 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.0x20.net", Issuer "mail.0x20.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47B821D99 for ; Sat, 3 Oct 2015 10:45:34 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id D90FE6DF91B; Sat, 3 Oct 2015 12:45:30 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id t93AjU3A065703; Sat, 3 Oct 2015 12:45:30 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id t93AjR3I064954; Sat, 3 Oct 2015 12:45:27 +0200 (CEST) (envelope-from lars) Date: Sat, 3 Oct 2015 12:45:27 +0200 From: Lars Engels To: Dirk Engling Cc: Maksim Yevmenkin , "freebsd-bluetooth@freebsd.org" Subject: Re: first shot at user friendly bluetooth-config script Message-ID: <20151003104527.GM43663@e-new.0x20.net> References: <56072A53.4010005@erdgeist.org> <5608199F.9020105@erdgeist.org> <560ECF93.4060804@erdgeist.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8WA4ILJSyYAmUzbY" Content-Disposition: inline In-Reply-To: <560ECF93.4060804@erdgeist.org> X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p23 User-Agent: Mutt/1.5.23 (2014-03-12) 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: Sat, 03 Oct 2015 10:45:35 -0000 --8WA4ILJSyYAmUzbY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 02, 2015 at 08:40:19PM +0200, Dirk Engling wrote: > On 30.09.15 23:30, Maksim Yevmenkin wrote: >=20 > > there is /usr.bin/bluetooth and /usr.sbin/bluetooth, so somewhere under > > one of those would be a good place, imo. >=20 > Added in phabricator under usr.bin/bluetooth for now. >=20 > https://reviews.freebsd.org/D3778 >=20 > > right. so, if pc-bsd is your goal, and, you can rely on graphical > > interface, then i would suggest to basically >=20 > 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. PC-BSD already has a small GUI for this. --8WA4ILJSyYAmUzbY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJWD7HHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tJKwIAMriBJ0y39yb/uWPH20Ayz7s M3j/SseZbXptVlJh5v+EaXxaOFtlo/GnSD7OPwTwA3bxiWF722r8hWxIGQWG6m1w BT8hd71vBRcpr5gnR4+aFxFLpuFYAHcty0qYAJsHDPIttCndRkHu7V0dEZw/KrgC hfkRcZ8BOI1ERAJOFqz+xpJG8IehzHg72uys0J+ojdbyWqHsJKpMF1VIRGfGh7BI 7cTR3e/tCQ6N6zF9ity721rmznk3OetXSFoJDdSekErcQ/fXogG9jHXH2juzqC1O rPaLMs/nqrDdrqsQpH8EfB61LG6J8eTJP4nPnJfR5z8KDs/CwmAbZCaecVbrNDQ= =FOPg -----END PGP SIGNATURE----- --8WA4ILJSyYAmUzbY--