linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: deprecated tools: rfcomm, can we un-deprecate it?
Date: Sun, 22 Dec 2019 11:04:40 +0100	[thread overview]
Message-ID: <0aad7250-65f9-3e4c-e5ca-434139a9ae64@message-id.googlemail.com> (raw)

Hi all,

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 fun,

	Stefan
-- 
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman

             reply	other threads:[~2019-12-22 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22 10:04 Stefan Seyfried [this message]
2019-12-26 20:40 ` deprecated tools: rfcomm, can we un-deprecate it? Marcel Holtmann
2019-12-31 17:35   ` Stefan Seyfried
2020-01-04 12:45     ` Stefan Seyfried
2020-01-04 13:18       ` Johan Hedberg
2020-01-07 13:49         ` Stefan Seyfried

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0aad7250-65f9-3e4c-e5ca-434139a9ae64@message-id.googlemail.com \
    --to=stefan.seyfried@googlemail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).