libbluetooth3-5.55-150300.3.14.1 < > , }\ cNjop9| Sw_jy".l6 rIkDh,v$^,-" ^}F `kIZjs>Lj@ʛQz]\F\ ==f+WP?LS6S` eX8 ݢBzdX&Gz(! tVK һrເC 6.dBȎoz*/Ml܄ zrEіLk εAn &d!~2(ǪcYϠ2ȷwIj > C tt ? td d # 7 ! , L \
l
< d ( 8 2 9 2 :
2 > o @ o B o F o G o H p I p, X p4 Y pD Z pp [ pt \ p| ] p ^ q b q c r/ d r e r f r l r u r v r w s x s y s z t t t t t` C libbluetooth3 5.55 150300.3.14.1 Bluetooth Libraries BlueZ provides support for the core Bluetooth layers and protocols.
It is uses a modular implementation. It has many interesting features:
* Multithreaded data processing
* Support for multiple Bluetooth devices
* Real hardware abstraction
* Standard socket interface to all layers
* Device and service level security support cNjosangiovese SUSE Linux Enterprise 15 SUSE LLC GPL-2.0-or-later https://www.suse.com/ System/Libraries http://www.bluez.org linux ppc64le $ e !K FVA큤A큤 cNjYcNj[cNjm^H9_T^mjcNjmHj 73fdc4d1a3fbd7ba305f3d0e60fee04213ced2844d2bd48fd9edc81842193bea b755ef7f8d52f660e25689b4169a85d5be0160ef44951cff38237b94633ebd9a 7b19b419af2bfe0dad76ee84daa3f28a22c939e98580a46fee6a4002c318736b 33deb9aa9bd8340506b652d37e17c166714f1fd19dcb27e94a5b8897596ee925 b499eddebda05a8859e32b820a64577d91f1de2b52efa2a1575a2cb4000bc259 libbluetooth.so.3.19.3 root root root root root root root root root root root root root root root root bluez-5.55-150300.3.14.1.src.rpm bluez-libs libbluetooth.so.3()(64bit) libbluetooth3 libbluetooth3(ppc-64) @ @
/sbin/ldconfig /sbin/ldconfig libc.so.6()(64bit) libc.so.6(GLIBC_2.17)(64bit) rpmlib(CompressedFileNames) rpmlib(FileDigests) rpmlib(PayloadFilesHavePrefix) rpmlib(PayloadIsXz) 3.0.4-1 4.6.0-1 4.0-1 5.2-1 4.14.3 cN@cN@b5@``P@_`]@]\@\I\
`[H@[4ZK@Zp^@ZF.@Z/YcYjY_wYOY9<@Y(Y
XZXXX@W
W@WgWV@WI@W
@@VV$@V3[V +UpUUc@U@UUU @UTи@T@T{T`jlee@suse.com jlee@suse.com jlee@suse.com acho@suse.com acho@suse.com acho@suse.com acho@suse.com acho@suse.com acho@suse.com acho@suse.com acho@suse.com seife+obs@b1-systems.com acho@suse.com acho@suse.com normand@linux.vnet.ibm.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com msuchanek@suse.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com tchvatal@suse.com seife+obs@b1-systems.com seife+obs@b1-systems.com jengelh@inai.de seife+obs@b1-systems.com fbui@suse.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com dimstar@opensuse.org seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com rguenther@suse.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com seife+obs@b1-systems.com - Add gatt-Fix-not-cleaning-up-when-disconnected.patch
- This patch includes the addition of a pending disconnect callback to handle
cleanup better if a disconnect occurs during a write, an acquire write
or read operation using bt_att_register_disconnect with the cb.
(bsc#1192394)(CVE-2021-43400)
- Add gatt-database-No-multiple-calls-to-AcquireWrite.patch - Add adapter-Fix-storing-discoverable-setting.patch
- discoverable setting shall only be store when changed via Discoverable
property and not when discovery client set it as that be considered
temporary just for the lifetime of the discovery.
(bsc#1188859)(CVE-2021-3658) - Add shared-gatt-server-Fix-heap-overflow-when-appending-.patch
- The code shall check if the prepare writes would append more the
allowed maximum attribute length. (bsc#1194704 CVE-2022-0204) - Add gatt-Fix-potential-buffer-out-of-bound.patch
* When client features is read check if the offset is within the cli_feat
bounds. (bsc#1187165 CVE-2021-3588)
- Add shared-gatt-db-Introduce-gatt_db_attribute_set_fixed.patch
* This enables user to inform if an attribute has a fixed length so it can
automatically perform bounds checking. (bsc#1187165 CVE-2021-3588)
- Add gatt-Make-use-of-gatt_db_attribute_set_fixed_length.patch
* This makes use of gatt_db_attribute_set_fixed_length so the database is
aware of the length of the values and perform bounds checking.
(bsc#1187165 CVE-2021-3588) - Add
shared-gatt-server-Fix-not-properly-checking-for-sec.patch
* Fix not properly checking for secure flags
(bsc#1186463 CVE-2021-0129 CVE-2020-26558) - update to 5.55:
* Fix issue with handling security level for HoG.
* Fix issue with handling HIDSDPDisable attribute.
* Fix issue with handling HID virtual cable unplug.
* Fix issue with handling HID channel disconnect order.
* Fix issue with handling AVDTP delay reporting states.
* Fix issue with handling AVRCP notification events.
* Fix issue with handling AVRCP list player attributes.
* Fix issue with handling AVRCP category 1 player settings.
* Fix issue with handling AVRCP media player passthrough bitmask.
* Fix issue with handling HFP 1.7 default features.
* Fix issue with handling GATT disconnecting handling.
* Fix issue with handling GATT database hash.
* Fix issue with handling service changed characteristic.
* Fix issue with handling read of multiple characteristic values.
* Fix issue with handling Just-Works auto-accept pairing.
* Fix issue with handling authentication of bonded devices.
* Fix issue with handling L2CAP streaming mode for AVDTP.
* Fix issue with handling SysEx parser for MIDI support.
* Fix issue with handling configured scan parameter values.
* Fix issue with handling temporary devices removal.
* Fix issue with handling advertising flags.
- update to bluez-5.54:
* Fix issue with HOGP to accept data only from bonded devices.
* Fix issue with A2DP sessions being connected at the same time.
* Fix issue with class UUID matches before connecting profile.
* Add support for handling MTU auto-tuning option for AVDTP.
* Add support for new policy for Just-Works repairing.
* Add support for Enhanced ATT bearer (EATT).
- update to bluez-5.53:
* Fix issue with handling unregistration for advertisment.
* Fix issue with A2DP and handling recovering process.
* Fix issue with udpating input device information.
* Add support for loading blocked keys.
- update to version 5.52:
* Fix issue with AVDTP session disconnect timeout handling.
* Mark media endpoint APIs as stable interfaces.
- update to version 5.51:
* Fix issue with first agent not being registered as default.
* Fix issue with loading devices without Service Changed CCC.
* Fix issue with GATT client and extended property reading.
* Fix issue with handling GATT client invalid read behavior.
* Fix issue with handling GATT disconnect handler removal.
* Fix issue with missing GATT/GAP service records for SDP.
* Fix issue with checking SDP continuation state length.
* Fix issue with HID device removal on HoG disconnect.
* Fix issue with AVDTP and session destroy handling.
* Fix issue with AVCTP and output MTU accounting.
* Fix issue with AVRCP and creating media items.
* Add support for GATT database caching feature.
* Add experimental support for Bluetooth Mesh Profile.
- update to version 5.50:
- Fix issue with GATT and reading long values.
- Fix issue with GATT and reading multiple includes.
- Fix issue with GATT and service changes when offline.
- Fix issue with handling secondary service discovery.
- Fix issue with handling persistency of CCC values.
- Fix issue with handling Mesh session on disconnection.
- Fix issue with handling Mesh proxy PDU SAR message length.
- Fix issue with handling Mesh default heartbeat TTL value.
- Add support for Mesh node-reset operation handling.
- Add support for GATT authorization request handling.
- Add support for GATT minimum key size requirements.
- Add support for GATT server and included services.
- Add support for handling additional advertising data.
- Add support for handling separate discoverable state.
- Add support for enabling HFP version 1.7 features.
- Add support for dedicated Bluetooth logging daemon.
- update to version 5.49:
This is mostly a bug fix release, with fixes to features such as
AVCTP, OBEX, GATT and Mesh. There are however some notable new
features also, such as improved heartbeat management support in
meshctl as well as a new experimental ConnectDevice D-Bus method
on the Adapter interface, which can be used for quick device
object creation for testing purpose or when information about the
device has been received over some Out-of-Band channel.
- Add --enable-external-ell to actually make use of pkgconfig(ell).
- remove obsolete upstreamed patches:
* 0001-obexd-use-AM_LDFLAGS-for-linking.patch
* 0001-core-Fixes-order-InterfaceAdded.patch
* tools-Fix-build-after-y2038-changes-in-glibc.patch
* hcidump-Fix-set_ext_ctrl-global-buffer-overflow.patch
* 0001-btmon-fix-segfault-caused-by-buffer-over-read.patch
* 0002-btmon-fix-segfault-caused-by-buffer-over-read.patch
* 0003-btmon-fix-segfault-caused-by-buffer-over-read.patch
* 0004-btmon-Fix-crash-caused-by-integer-underflow.patch
* 0005-btmon-fix-stack-buffer-overflow.patch
* 0006-btmon-fix-multiple-segfaults.patch
* 0007-btmon-fix-segfault-caused-by-integer-underflow.patch
* 0008-btmon-fix-segfault-caused-by-integer-undeflow.patch
* 0009-btmon-fix-segfault-caused-by-buffer-over-read.patch
* 0010-btmon-fix-segfault-caused-by-buffer-overflow.patch
* 0011-btmon-fix-segfault-caused-by-integer-underflow.patch
* 0012-btmon-fix-segfault-caused-by-buffer-over-read.patch
- use autopatch, spec-cleaner
- refresh other patches - Add tools-Fix-build-after-y2038-changes-in-glibc.patch
* The 32-bit SIOCGSTAMP has been deprecated. Use the deprecated
name to fix the build.(bsc#1156544) - Add
hcidump-Fixed-malformed-segment-frame-length.patch
* Ensure the L2CAP SDUs whose length field match the actual frame
length.(bsc#1013712)(CVE-2016-9798)
- Modify bluez.changes:
Remove (bsc#1013712)(CVE-2016-9798) tag from patch
hcidump-Add-assoc-dump-function-assoc-date-length-ch.patch - Add
hcidump-Add-assoc-dump-function-assoc-date-length-ch.patch
* amp_assoc_dump() didn't check the length of amp assoc struct.
(bsc#1013712)(CVE-2016-9798)(bsc#1013708)(CVE-2016-9797)
Add hcidump-Fix-memory-leak-with-malformed-packet.patch
* Do not allow to read more than allocated data buffer size.
(bsc#1015171)(CVE-2016-9917)
- Refresh patches:
patches/bluez-cups-libexec.patch
patches/bluez-5.45-disable-broken-tests.diff
- fix bluez.changes:
add (bsc#1013893)(CVE-2016-9802) tag for last log. - Add:btmon: multiple memory management vulnerabilities fixed
Multiple different memory management vulnerabilities were discovered
in btmon while fuzzing it with American Fuzzy Lop. Purpose of this
fuzzing effort was to find some bugs in btmon, analyse and fix them
but also try to exploit them. Also goal was to prove that fuzzing is
low effort way to find bugs that could end up being severe ones.
Most common weakness appeared to be buffer over-read which was
usually caused by missing boundary checks before accessing array.
Integer underflows were also quite common. Most interesting bug was
simple buffer overflow that was actually discovered already couple
years ago by op7ic:
https://www.spinics.net/lists/linux-bluetooth/msg68898.html
but it was still not fixed. This particular vulnerability ended up
being quite easily exploitable if certain mitigation technics were
disabled.(bsc#1015173)(CVE-2016-9918)(bsc#1013893)(CVE-2016-9802)
0001-btmon-fix-segfault-caused-by-buffer-over-read.patch
0002-btmon-fix-segfault-caused-by-buffer-over-read.patch
0003-btmon-fix-segfault-caused-by-buffer-over-read.patch
0004-btmon-Fix-crash-caused-by-integer-underflow.patch
0005-btmon-fix-stack-buffer-overflow.patch
0006-btmon-fix-multiple-segfaults.patch
0007-btmon-fix-segfault-caused-by-integer-underflow.patch
0008-btmon-fix-segfault-caused-by-integer-undeflow.patch
0009-btmon-fix-segfault-caused-by-buffer-over-read.patch
0010-btmon-fix-segfault-caused-by-buffer-overflow.patch
0011-btmon-fix-segfault-caused-by-integer-underflow.patch
0012-btmon-fix-segfault-caused-by-buffer-over-read.patch - Add hcidump-fixed-hci-frame-dump-stack-buffer-overflow.patch
to replace
CVE-2016-9800-tool-hcidump-Fix-memory-leak-with-malformed-packet.patch
(PATCH-FIX-UPSTREAM)(bsc#1013721)(CVE-2016-9800)
Add hcidump-Fix-set_ext_ctrl-global-buffer-overflow.patch
to fix global buffer overflow (PATCH-FIX-UPSTREAM)
(bsc#1013732)(CVE-2016-9801)
- Fix %ifarch range. - add 0001-core-Fixes-order-InterfaceAdded.patch (boo#1101119)
to fix headset connect after suspend/resume - Add lost patches for RPi3 bluetooth support (bsc#995059)(bsc#1094902)
0001-rpi3-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
0002-rpi3-Move-the-43xx-firmware-into-lib-firmware.patch - Add
CVE-2016-9800-tool-hcidump-Fix-memory-leak-with-malformed-packet.patch
* Fix hcidump memory leak in pin_code_reply_dump().
(bsc#1013721)(CVE-2016-9800)
CVE-2016-9804-tool-hcidump-Fix-memory-leak-with-malformed-packet.patch
* Fix hcidump buffer overflow in commands_dump().
(bsc#1013877)(CVE-2016-9804) - Add disable_some_obex_tests.patch bypass boo#1078285 for PowerPC - update to version 5.48:
This release brings many fixes and feature enhancements.
Some notable enhancements include support for devices with the
BLE battery service, as well as improved Mesh support in the
meshctl tool. Several previously experimental D-Bus APIs have now
been marked as stable, notably the Advertising Manager API as
well as the AquireWrite & AquireNotify GATT APIs.
As far as fixes go, these can be found in many areas of the stack,
including A2DP, AVCTP, device discovery, Mesh, and GATT. - add 0001-obexd-use-AM_LDFLAGS-for-linking.patch
- document systemd dependency during %post - update to version 5.47:
This release contains various fixes to GATT, A2DP and BR/EDR vs
LE bearer handling. There’s also a notable SDP fix for CVE-2017-
1000250 (part of the recently announced BlueBorne vulnerabilities).
Feature-wise, there’s now support for adding the appearance and
local name to advertising data through the Advertising D-Bus
interface. The btmon tool is now also able to better decode most
Bluetooth 5.0 HCI commands and events.
The Bluetooth Mesh Profile specification was released recently,
and this BlueZ release comes with initial support for it in the
form of a new meshctl tool. Using this tool it’s possible to
provision mesh devices through the GATT Provisioning Bearer
(PB-GATT), as well as communicate with them (e.g. configure them)
using the GATT Proxy protocol. - update to version 5.46:
* Fix issue with handling ATT over BR/EDR connections.
* Fix issue with SDP browsing cleanup after connection.
* Fix issue with pointer dereference and OPP Put request.
* Fix issue with identity address updates during pairing.
* Fix issue with not removing services that had disappeared.
* Add support for improved discovery of included services.
* Add support for simplified characteristics discovery.
* Add support for GATT caching configuration option.
* Add experimental support for AcquireWrite and AcquireNotify. - enable sixaxis plugin - Add %post/%postun to bluez-auto-enable-devices so the settings
change takes effect (boo#1039476) - add bluez-auto-enable-devices subpackage with main.conf which
auto-enables all devices (boo#1039476) - add bluez-5.45-disable-broken-tests.diff to disable two broken
tests (reported upstream but not yet fixed) - update to version 5.45:
This is mostly a bugfix release with fixes in ATT, GATT, OBEX
and AVDTP.
Feature-wise there are some new things as well, such as btmon
support decoding Bluetooth 5.0 HCI commands and events. - make testsuite run non-parallel (it has problems with running
parallel checks) and quiet - update to version 5.44:
Most fixes are LE (specifically GATT) related, however some other
areas are affected as well.
Feature-wise, there’s a new MIDI plugin and support for using
single-mode (LE-only) controllers that lack a public address.
E.g. any nRF5x controller running a MyNewt or Zephyr based
firmware falls into this category.
- packaging: add "--enable-midi", "--enable-deprecated"
TODO: package deprecated tools into separate package to prepare
removal some time in the future
- rebase bluez-cups-libexec.patch - Set the cupsdir directly with patch instead of mv and seds:
* bluez-cups-libexec.patch
- Replace requirements by the pkgconfig counterparts
* this should solve out the problem with builcycle on Factory
- Ran over with spec-cleaner - update to version 5.43:
This is almost purely a bug-fix release with fixes to HoG, ATT
and PAN. There’s also a fix for a regression in 5.42 that caused
connection failures for external profiles like OBEX.
Feature-wise there’s one notable addition: LE privacy. By
enabling this in main.conf it’s now possible to make BlueZ
generate a local Identity Resolving Key (IRK) and use Resolvable
Private Addresses (RPAs) for itself. - update to version 5.42:
The major API change with this release is that the GATT D-Bus API
is no longer marked as experimental.This should hopefully
encourage the creation of more applications using it. Feature-
wise, btmon received support for decoding full mgmt message
traces - a feature that is available in the bluetooth-next kernel
tree, i.e. on its way to the 4.9 kernel release. In addition to
these changes, this release contains also fixes in areas such as
PBAP, transport selection (BR/EDR vs LE), ATT and A2DP. - Update descriptions a bit. Adjust RPM groups for what is used
in openSUSE normally. Drop archaic %clean section.
Drop --with-pic which is only for (unbuilt) static libs. - update to version 5.41:
BlueZ 5.41 is purely a bug-fix release targeting areas such as
GATT, AVRCP, OBEX and device discovery filters. The GATT D-Bus
API is now starting to be stable enough that this will likely be
the last release where it is flagged as experimental.
- fix build with older distributions that don't have %_userunitdir
ins systemd-rpm-macros - Don't require systemd-devel but systemd-rpm-macros (bsc#983167)
Bluez simply needs to know where the systemd default paths are, at
build time. For that there's no need to build-require systemd or
systemd-devel (and pull all theirs dependencies). Instead
build-require systemd-rpm-macros, which has much less dependencies. - update to version 5.40:
This is mostly a bug fix release fixing issues with GATT, paired
devices and connection handling (particularly for accepting
connections through the Profile D-Bus interface).
One new feature is the ability to use btmon for reading HCI logs
from a TTY device. Right now the creation of this kind of logs is
available with Zephyr in the
form of a special console logging mode (more information
available here
https://www.zephyrproject.org/doc/board/arduino_101_ble.html#getting-hci-traces>).
The format of the protocol is a slight modification of what btmon
normally receives from the kernel monitor sockets, and is
documented in doc/btsnoop.txt). - update to version 5.39:
This is almost entirely a bug fix release with important fixes to
GATT, HoG, AVRCP & A2DP.
- install gatttool, needed for bluetooth 4.0 devices (boo#970628) - update to version 5.38:
This release has lots of updates and fixes to the GATT D-Bus API.
It should be working considerably better now. A key change to the
GATT D-Bus API is that it is now fully conforming to the word of
the D-Bus Object Manager specification. Instead of registering
each service individually with an Object Manager interface per
service path, all application services are now grouped together
through a single RegisterApplication call. The details can be
found in gatt-api.txt. Besides the D-Bus API change there are
also numerous fixes to GATT functionality in general.
Other areas that received fixes in this release are OBEX, AVRCP
and 128-bit UUID handling. Feature-wise there isn’t anything
groundbreaking, but a notable update is support for the Start
Limited Discovery command in the btmgmt tool (this feature
debuted with the 4.5 kernel release).
* Fix issue with stack overflow and UUID handling.
* Fix issue with ObjectManager interface and GATT.
* Fix issue with GATT database and error handling.
* Fix issue with GATT client notifications.
* Fix issue with GATT object ordering.
* Fix issue with GATT default MTU exchange.
* Fix issue with device attribute clearing.
* Fix issue with AVRCP capabilities request. - update to version 5.37:
* Fix issue with registering external profiles.
* Fix issue with connecting external profiles.
* Fix issue with GATT service changed handling.
* Fix issue with not emitting GattServices update.
* Convert to unified HID over GATT profile support.
* Convert to KeyboardDisplay as default IO capability.
* Install btattach utility by default. - update to version 5.36:
This release consists for the most part of bug fixes that target
areas such as PBAP, AVRCP and GATT.
Feature-wise a notable change is btmon support for vendor
diagnostic messages which will be debuting with the 4.4 Linux
kernel release. This feature will allow e.g. LMP tracing with
specific controllers. For now there is preliminary support for
Intel and Broadcom based controllers.
- update dbus-devel buildrequires from configure.ac
- remove obsolete bluez-no-duplicate-test-names.patch - update to version 5.35:
This release contains bugfixes to areas such as GATT, OBEX, HoG
and AVRCP. From now on bluetoothd will cache more information of
remote GATT databases and thereby avoid unnecessary rediscovery
of remote services.
A noteworthy new feature is the ability to configure bluetoothd
to automatically enable (power on) all new adapters. One use of
this is to replace unreliable "hciconfig hci0 up" commands that
some distributions use in their init/udev scripts. The feature
can be enabled by having "AutoEnable=true" under the "[Policy]"
section of /etc/bluetooth/main.conf - Add bluez-no-duplicate-test-names.patch: Fix test suite when
running against GLIB 2.45.x (test names are not to be used
duplicated). - update to version 5.34:
This release fixes a fairly important bug for the GATT D-Bus
interface where automatic reconnections would not always occur
for the client role. There’s also a fix for a missing attribute
in PBAP & MAP SDP records as well as a couple of audio related
fixes. A new feature in this release is Media Player Selection
support for the Target role of AVRCP (the Controller role already
had this). - update to version 5.33:
This release contains mostly bugfixes, particularly in areas such
as the audio plugin, GATT and OBEX. The main feature additions
are in the the emulator code which received improvelents to LE
features. There’s also a new tool for testing the recently
released Eddystone protocol from Google. - update to version 5.32:
This is mostly a bug fix release rather than including many new
features. The fixes fall in several different areas, including
OPP, ATT and advertising (instance number handling in
particular). There’s also a fix for handling a sudden disconnect
when a connection setup process hasn’t yet completed. The one
notable feature this release has is the ability to select between
letting the stack handle ATT security elevation or doing the
respective error handling in higher layers. - update to version 5.31
Fixes to many different areas, including networking, GATT, HID,
A2DP and AVRCP. Feature-wise we’ve got support for security flags
for the GATT database, allowing fine-grained security level
control for D-Bus clients using the GATT D-Bus API. We’ve also
got a new experimental device discovery filter interface which
allows filtering for a specific remote service, RSSI threshold
or transport (LE vs. BR/EDR). Another new experimental interface
is for LE advertising, which also brings the LE peripheral role
closer to feature completion on a D-Bus level
- remove obsolete bluez-5.30-disable-broken-tests.diff - update to version 5.30
The highlight of this release is the completion of the GATT D-Bus
APIs. We’ve now got both the client and server functionality in
place, however it’s still behind the -E (--experimental) command
line switch. The API is documented in doc/gatt-api.txt and there
are several test tools for it in the tree (even bluetoothctl has
support for it). Another new (and still experimental) D-Bus API
that debuts with this release is one for managing LE Advertising,
i.e. acting in peripheral role. The API is documented in
doc/advertising-api.txt.
Besides the new features, there are several fixes to AVCTP, AVDTP
& AVRCP. There’s also a fix for C++ compiler compatibility with
the library headers as well as a fix for device information not
being stored in certain corner cases.
- add bluez-5.30-disable-broken-tests.diff to fix test suite
- remove -fstack-reuse=none workaround
- remove 20150312-PATCH_BlueZ_shared_gatt-client_Fix_invalid_read-56974.patch - Build the testsuite with -fstack-reuse=none to workaround broken
test setup. [bnc#923768] - update to version 5.29
This is a comparatively large release with over a month and 475
commits since 5.28. There have been lots of fixes to the Android
side. Our internal GATT library (used both by ‘normal’ BlueZ as
well as the Android version) received lots of updates for this
release. Other notable changes are a fix for AVCTP key repeat
timeout as well as added support for the Multi Profile
Specification (MPS).
- add 20150312-PATCH_BlueZ_shared_gatt-client_Fix_invalid_read-56974.patch
from bluez-devel for fixing test case failure (will be included in
next bluez release) - update to version 5.28
Here’s the first BlueZ release in 2015. Most of the changes since
the last one are bug fixes, but there’s actually quite many of
them this time, including:
* Fixes to GATT service discovery & probing
* Fix for bearer selection with dual-mode devices
* Fix potential crash when removing devices
* Fix issue with incomplete names in EIR data
* Fix parsing GATT name characteristics
* Fix AVCTP long press & key repetition handling
* Fixes for GATT notification handling
Besides bug fixes we’ve now also got more extensive unit tests
for new GATT code as well as better HCI decoders in btmon for
some less used 4.1 and 4.2 features. The hid2hci tool gained
support for CSR 8510 A10 devices and the hex2hcd tool received a
complete rewrite with better command handling. - update to version 5.27
Here comes the traditional x-mas release!
BlueZ 5.27 consists mostly of bug fixes to areas such as GATT
and mgmt (the interface through which bluetoothd talks to the
kernel). The emulation framework has also received many new
features, paving the way for more extensive test automation. - update to version 5.26
This release is for the most part a bug-fix release with fixes in
A2DP and OBEX related functionality, but there’s also an added
features for get/set reports for HID over GATT as well as
Phonebook Access Profile 1.2 support
The Bluetooth 4.2 specification went public in early December and
BlueZ 5.26 is the first release with support for its features.
Perhaps the most notable one of these is Low Energy Secure
Connections which will require a 3.19 or newer kernel. This
feature brings LE pairing to the same level of security as it has
been for BR/EDR. LE SC also brings along with it so-called
cross-transport pairing, which means that you only need to pair
once over LE or BR/EDR to get the necessary keys for both
transports between two dual-mode devices. - update to version 5.25
This release contains various improvements to MAP and PBAP
support. There are also various GATT related fixes. We’ve also
got a fix for a race condition which could occasionally cause LE
connection/pairing failures. The fix will work for kernels from
3.13 onward (for older kernels a proper fix isn’t really feasible).
- packaging: remove obsolete README.SUSE and README.packagers /sbin/ldconfig /sbin/ldconfig bluez-libs sangiovese 1666083439 3.36 5.55-150300.3.14.1 5.55-150300.3.14.1
3.36 libbluetooth.so.3 libbluetooth.so.3.19.3 libbluetooth3 AUTHORS ChangeLog README libbluetooth3 COPYING /usr/lib64/ /usr/share/doc/packages/ /usr/share/doc/packages/libbluetooth3/ /usr/share/licenses/ /usr/share/licenses/libbluetooth3/ -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g obs://build.suse.de/SUSE:Maintenance:26460/SUSE_SLE-15-SP3_Update/d4548572b70b8fdca7a0da3f06ea6996-bluez.SUSE_SLE-15-SP3_Update drpm xz 5 ppc64le-suse-linux ELF 64-bit LSB shared object, 64-bit PowerPC or cisco 7500, version 1 (SYSV), dynamically linked, BuildID[sha1]=4f16aff047bb2e4d03a0a93c4772396892cf6426, stripped directory UTF-8 Unicode text ASCII text P R R .r\? utf-8 e44d248c5c5662e8f90df8885b8714500a8ada1b98ae361f960991e99ec59e8c ? 7zXZ
! t/DN] "k%{ ,l yS`@z Ў@
cд 7{yM8]gW; .`]"@X<ڷ'>鎁t@\qQKgcfVA&t#Yh:7Vgcț$NFg ,
}OƊ}V>SIX݁UFɣڄ_exqx_ч`< ./$n{Ro&'ZG"=*jn9!k@Zm6ķ_lM=NE[fQUczMr&'"i,YΡ
H>5>2_ag#̴+RigĊ] /(
gQ"ZRAʼga
tj~4wH+"RbD|fU W:?_S>EQ^hU*1y}s,&V /m&(?} > a `m{Zn 甒zqV}H_O:gXe}I "D2b&,A4T33͇}4I },[L5"Ϛze;% g
ZvF5]~*hDicc 0?/72 \63ҽf,~jvr|$3hy9J(A) t*<|{)&Lqq `jc @"b< WDGVkq
f/y~3KO[Xpӳ3UQc.uB
0&Ą0|mAE5ۈedH6hݚḁhrn24s<>AZF)Fm# х3\PPJzjäޓ*P cֽq%jcF4;-u\a0Y0:+,-/u=Q~Abo\7) bY](i1 Ёiĵn
% ]>=W
M'PFἧa' * }t
YZ