bluez-devel-5.48-lp151.8.15.1<>,e_෸/=„a8j^LDC?@mfH%5 Z@Ez =g& '3OMk0*eJ+}CyC9CHɘи!jq5i\݈=mgɽTD)_q>s Ն@[llXh]uo{d3G:io+j Db$0h%S!̑6y3m ;oufn/U>>]<?],d  C $\ x    8~Ph(8.9.: .FXGXHY IYDXYTYY`\Y]Y^Z?bZc[Ad[e[f[l[u[v\$w\Tx\y\z\\\\](Cbluez-devel5.48lp151.8.15.1Files needed for BlueZ developmentFiles needed to develop applications for the BlueZ Bluetooth protocol stack._cloud112*openSUSE Leap 15.1openSUSEGPL-2.0+http://bugs.opensuse.orgDevelopment/Languages/C and C++http://www.bluez.orglinuxi586$b@<(' GTA큤______________20c33db1a6a2bde76c2be5865c50e4a94b2474b746d1ddfa9df53ff3fc7355779091258865eb4adfc20907101280e8d13b2bdcdfbd92243efc755252f2d61de44719bedd852a08e8b776a096cd0ca8927654e8c5a730a50355e233df3d71ff5da4ebf3abe24194d881aeaf8fbbda00531d2c0cc7c4897557fbf8536c40b981297c3f8d2f2831c137aac5a7cfa7bc8d5acbc98188399be9cb894c03160e84ad29de2d96de4856511615252fa2f658a878e83c0323dd88574d1fbc774cf4f4fc392a9970a87f41b81b9c63a257c409b4d424aa6bab8d580005227239743ca06b2a971e4885f82ecc544e4f49e3bfa40005aa8b454b7df9850aec9e37b5b9ef7b78dd3fc980d197e7bade071d5bc3b3890b9693cdb58f993dd4c07686cba626e71c1790b620e5322d4d5671ea75029d9efc0f76ebbe34361a65ca101bba126d43f91034c0e8945af85675538d5166fbdec069b88340bbacea0f8fdde577caee1e8100d762bc7c7bc1e81a10b4f971fd49688889435df34292d14714d856a75a2c4dlibbluetooth.so.3.18.16rootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootbluez-5.48-lp151.8.15.1.src.rpmbluez-develbluez-devel(x86-32)pkgconfig(bluez)@    /usr/bin/pkg-configlibbluetooth3rpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)5.483.0.4-14.6.0-14.0-15.2-14.14.1_t@^r @]@]\@\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`Al Cho Al Cho Al Cho Al Cho Al Cho Al Cho Al Cho seife+obs@b1-systems.comacho@suse.comacho@suse.comnormand@linux.vnet.ibm.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.commsuchanek@suse.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comtchvatal@suse.comseife+obs@b1-systems.comseife+obs@b1-systems.comjengelh@inai.deseife+obs@b1-systems.comfbui@suse.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comdimstar@opensuse.orgseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comrguenther@suse.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.comseife+obs@b1-systems.com- Add shared-att-Fix-possible-crash-on-disconnect.patch * Fix possible crash on disconnect.(bsc#1177895)(CVE-2020-27153)- Add HOGP-must-only-accept-data-from-bonded-devices.patch HOGP 1.0 Section 6.1 establishes that the HOGP must require bonding.(bsc#1166751)(CVE-2020-0556) HID-accepts-bonded-device-connections-only.patch This change adds a configuration for platforms to choose a more secure posture for the HID profile.(bsc#1166751)(CVE-2020-0556) input-hog-Attempt-to-set-security-level-if-not-bonde.patch Attempt to set security level if not bonded. (bsc#1166751)(CVE-2020-0556) input-Add-LEAutoSecurity-setting-to-input.conf.patch Add LEAutoSecurity setting to input.conf. (bsc#1166751)(CVE-2020-0556)- 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.packagerscloud112 1604575415 5.48-lp151.8.15.15.48-lp151.8.15.15.48bluetoothbluetooth.hbnep.hcmtp.hhci.hhci_lib.hhidp.hl2cap.hrfcomm.hsco.hsdp.hsdp_lib.hlibbluetooth.sobluez.pc/usr/include//usr/include/bluetooth//usr/lib//usr/lib/pkgconfig/-fomit-frame-pointer -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.opensuse.org/openSUSE:Maintenance:14902/openSUSE_Leap_15.1_Update/90a1600fe64c6a58431eb495f5cd8ce9-bluez.openSUSE_Leap_15.1_Updatedrpmxz5i586-suse-linuxdirectoryC source, ASCII textpkgconfig filePREOaa6+utf-857b8a2628603964b15179cc5fb57edf16b74c00c69748a7919320ac2ed8f0e32? 7zXZ !t/Y]"k%w}R]RZ{OMd!%AȘezg'QFߎiw02Pv\ރAYnƢBQ~>vHeRNrՍ(Zn3Z2-P}1怕 0!T5=yfQ:̠*JJ@Iap+SLCcq(j.s5 YZ