From: Alexander Holler <holler@ahsoftware.de>
To: Harald Schmitt <linux@hschmitt.de>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: Why doesn't plugins/sixaxis.c set devices as Trusted?
Date: Thu, 09 Jul 2015 22:26:39 +0200 [thread overview]
Message-ID: <559ED8FF.2000800@ahsoftware.de> (raw)
In-Reply-To: <559BDF20.9090905@hschmitt.de>
Am 07.07.2015 um 16:16 schrieb Harald Schmitt:
> Am 07.07.2015 um 06:31 schrieb Alexander Holler:
>> 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.
> Just as a side note: This is not a good security rule. Why should I
> trust a game controller on any other service then controlling my game
> moves?
Also differentiating a network service from an input service wouldn't be
that hard (at least at OS level), it won't help much in regard to the
topic because you can't really differentiate a gamepad from a keyboard
(both are HID input devices).
And you just don't want to automatically enable (trust) a (wireless)
remote input (especially a keyboard) if someone managed it to plug in
some USB device into your Linux box without any user interaction.
Regards,
Alexander Holler
prev parent reply other threads:[~2015-07-09 20:26 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
2015-07-07 14:16 ` Harald Schmitt
2015-07-09 20:26 ` Alexander Holler [this message]
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=559ED8FF.2000800@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux@hschmitt.de \
/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.