Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
Subject: Re: deprecated tools: rfcomm, can we un-deprecate it?
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <0aad7250-65f9-3e4c-e5ca-434139a9ae64@message-id.googlemail.com>
Date:   Thu, 26 Dec 2019 21:40:16 +0100
Cc:     BlueZ devel list <linux-bluetooth@vger.kernel.org>
Content-Transfer-Encoding: 7bit
Message-Id: <2203E98B-B581-4C14-94DF-164D7E036234@holtmann.org>
References: <0aad7250-65f9-3e4c-e5ca-434139a9ae64@message-id.googlemail.com>
To:     Stefan Seyfried <stefan.seyfried@googlemail.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Stefan,

> as the bluez package maintainer for openSUSE, I'm trying to transition
> the package to build without "--enable-deprecated".
> 
> Now the users started asking me what to use as a replacement for the
> deprecated tools.
> 
> For many of the tools, the answer is "just use bluetoothctl and let
> bluetoothd handle things" (hciconfig, hcitool, sdptool)
> 
> But for rfcomm, I have not been able to find a suitable replacement.
> 
> All the other implementations of rfcomm services that I could find in a
> quick search (some python modules, blueman) just basically reimplement
> the functionality of rfcomm (socket(), bind(), connect(), ioctl()...),
> some of them in really odd / crazy ways, which is probably not the way
> to go...
> 
> So is there a way to set up a rfcomm device via bluetoothctl? I could
> not find one, but maybe I did not look hard enough?
> 
> If not, could we please un-deprecate rfcomm, because having everyone out
> there reinvent the functionality in crazy ways probably is not a good idea.
> 
> Or should I just continue to build the package with --enable-deprecated?
> But that will ship tools with known unfixed security issues (hcidump).

have a look at doc/profile-api.txt.

Regards

Marcel