Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Bluetooth Security
#6
I had this text file from a while back. I don't know if it still applies but maybe someone can test it out and report back.

Code:
There are two useful ways of running the agent:

1. sudo /var/www/daemon/blu_agent.py --agent --disable_pair_mode_switch --pair_mode

This simply runs the agent in such a way that it will accept any and all pairing requests and authorise them.

2. sudo /var/www/daemon/blu_agent.py --agent

This will start the agent in a mode that will reject all pairing requests by default. However, at the same time, it registers itself as a dbus service and waits to be instructed to enter pairing mode.

This will activate pairing mode for 30 seconds.

sudo /var/www/daemon/blu_agent.py --pair_mode --timeout 30

The idea of the second mode is, that pairing is disabled by default, but the gui offers a "PAIR" button to temporarily activate it - similarly how many commercial bluetooth devices do it.

It is also possible to instruct a running agent to activate pairing indefinitely (don't give a --timeout) or to disable pairing (--disable_pair_mode). Thus, the state of a running agent can be controlled completely without needing to restart it.

My suggestion would be to integrate the agent in such a way that it always runs. The user can then choose whether pairing should be always open or only open upon pressing the "PAIR" button. The gui would then change the mode of the running agent accordingly.

Until such time that the gui supports this, option (1) might be used as a default to open enable pairing for all.

If you launch the agent from a start up script, you might want to add --wait_for_bluez. The reason is, that it takes quite a while until buetoothd is available after system boot. With this option, the agent will retry to make the dbus connection instead if failing with an error.

/etc/dbus-1/system.d/moode.conf

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

<!-- ../system.conf have denied everything, so we just punch some holes -->

<policy user="root">
  <allow own="org.moodeaudio.bluez.agent"/>
  <allow send_destination="org.moodeaudio.bluez.agent"/>
  <allow send_interface="org.moodeaudio.bluez.agent.PairMode"/>
</policy>

<!-- allow users of bluetooth group to communicate -->
<policy group="bluetooth">
  <allow send_destination="org.moodeaudio.bluez.agent"/>
</policy>

<policy at_console="true">
  <allow send_destination="org.moodeaudio.bluez.agent"/>
</policy>

<!-- allow users of lp group (printing subsystem) to
     communicate with bluetoothd -->
<policy group="lp">
  <allow send_destination="org.moodeaudio.bluez.agent"/>
</policy>

<policy context="default">
  <deny send_destination="org.moodeaudio.bluez.agent"/>
</policy>

</busconfig>
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply


Messages In This Thread
Bluetooth Security - by windows97 - 01-02-2024, 04:24 PM
RE: Bluetooth Security - by Tim Curtis - 01-02-2024, 06:38 PM
RE: Bluetooth Security - by betarho - 01-03-2024, 10:42 AM
RE: Bluetooth Security - by Tim Curtis - 01-03-2024, 11:41 AM
RE: Bluetooth Security - by jakste - 04-06-2024, 08:53 PM
RE: Bluetooth Security - by Tim Curtis - 04-06-2024, 09:47 PM
RE: Bluetooth Security - by jakste - 04-06-2024, 10:01 PM
RE: Bluetooth Security - by jakste - 04-07-2024, 07:26 AM
RE: Bluetooth Security - by jakste - 04-08-2024, 08:21 PM
RE: Bluetooth Security - by Tim Curtis - 04-08-2024, 09:10 PM

Forum Jump: