All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Alexander Holler <holler@ahsoftware.de>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Cc: Szymon Janc <szymon.janc@tieto.com>
Subject: Re: Why doesn't plugins/sixaxis.c set devices as Trusted?
Date: Tue, 07 Jul 2015 07:35:07 +0200	[thread overview]
Message-ID: <1436247307.26954.17.camel@hadess.net> (raw)
In-Reply-To: <1436245912.26954.15.camel@hadess.net>

On Tue, 2015-07-07 at 07:11 +0200, Bastien Nocera wrote:
> On Tue, 2015-07-07 at 06:31 +0200, Alexander Holler wrote:
> > Am 06.07.2015 um 15:17 schrieb Bastien Nocera:
> > > Hey,
> > > 
> > > I don't understand the reason why plugins/sixaxis.c doesn't set 
> > > the
> > > device as trusted when plugged in.
> > 
> > It's because of security. If you trust a bluetooth device on Linux, 
> > 
> > you're trusting it for all services. In case of the sixaxis it 
> > means 
> > you're not only trusting it (the BT-MAC) as an input device, but 
> > also 
> > as 
> > a network device.
> > 
> > Now if you trust any plugged in device which says it's a sixaxis, I 
> > 
> > would tell my arduino to say it's an sixaxis with a MAC from one of 
> > 
> > my 
> > BT-dongles to get a magic device which gives me wireless remote 
> > access 
> > on every linux box with BT when I plug it in once.
> > 
> > That means you want user interaction, besides just plugging in a 
> > device.
> 
> What should the pairing process look like then? Because the current
> workflow is absolutely dreadful.

To solve that problem, I would:
1) disable the pairing altogether if there's no agent running
2) request auth to connect to the computer when the device is getting
plugged in, not X minutes later when you want to start using the joypad
wirelessly


  parent reply	other threads:[~2015-07-07  5:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 13:17 Why doesn't plugins/sixaxis.c set devices as Trusted? Bastien Nocera
2015-07-07  4:31 ` Alexander Holler
2015-07-07  5:11   ` Bastien Nocera
2015-07-07  5:34     ` Alexander Holler
2015-07-07  6:49       ` Alexander Holler
2015-07-07  5:35     ` Bastien Nocera [this message]
2015-07-07 14:16   ` Harald Schmitt
2015-07-09 20:26     ` Alexander Holler

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=1436247307.26954.17.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=holler@ahsoftware.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@tieto.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.