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