# Description: restart the service on errors
# Upstream: not-yet
# Description: restart the service on errors
# Upstream: not-yet
#
Gbp-Pq: Name ubuntu_error_restart.patch
LEAutoSecurity can be used to enable/disable automatic upgrades of
security for LE devices, by default it is enabled so existing devices
that did not require security and were not bonded will automatically
upgrade the security.
Note: Platforms disabling this setting would require users to manually
bond the device which may require changes to the user interface to
always force bonding for input devices as APIs such as Device.Connect
will no longer work which maybe perceived as a regression.
Gbp-Pq: Name CVE-2020-0556-4.patch
This attempts to set the security if the device is not bonded, the
kernel will block any communication on the ATT socket while bumping
the security and if that fails the device will be disconnected which
is better than having the device dangling around without being able to
communicate with it until it is properly bonded.
Gbp-Pq: Name CVE-2020-0556-3.patch
This change adds a configuration for platforms to choose a more secure
posture for the HID profile. While some older mice are known to not
support pairing or encryption, some platform may choose a more secure
posture by requiring the device to be bonded and require the
connection to be encrypted when bonding is required.
Reference:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00352.html
Gbp-Pq: Name CVE-2020-0556-2.patch
The PBAP ebook plugin is currently not included in the release tarballs
so we have to bring this back from the corresponding git tree on our
own.
Gbp-Pq: Name 0001-obexd-plugins-import-PBAP-ebook-support-from-upstrea.patch
Since commit 1455cf8dbfd0 ("driver core: emit uevents when
device is bound to a driver") the kernel started emitting
"bind" and "unbind" uevents which confuse the hid2hci
udev rules.
The symptoms on an affected machine (Dell E5400 in my case)
include bluetooth devices not appearing and udev hogging
the cpu as it's busy processing a constant stream of these
"bind"+"unbind" uevents.
Change the udev rules not do anything except for "add" and
"change" events. This seems to cure my machine at least.
v2: Don't mess up "change" (Zbyszek)
Fix up the commit message a bit
Closes: #931304
Origin: upstream, https://lore.kernel.org/patchwork/patch/1021109/
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931304
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836
Gbp-Pq: Name lp1759836.patch
Instead of trying to do it by hand. This also makes sure that
relative paths aren't used by the agent.
Gbp-Pq: Name 0001-obex-Use-GLib-helper-function-to-manipulate-paths.patch
http://www.spinics.net/lists/linux-bluetooth/msg38490.html
From 3027cb7141fb65cf3eeda69c688db8c4045e2d3f Mon Sep 17 00:00:00 2001
From: Giovanni Campagna <gcampagna-cNUdlRotFMnNLxjTenLetw@public.gmane.org>
Date: Sat, 12 Oct 2013 17:45:25 +0200
Subject: [PATCH] Allow using obexd without systemd in the user session
Not all sessions run systemd --user (actually, the majority
doesn't), so the dbus daemon must be able to spawn obexd
directly, and to do so it needs the full path of the daemon.
Gbp-Pq: Name 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch
zhouganqing