| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
It is no longer guaranteed the string will match since bt_uuid_to_string
now always uses 128 Bits format to be consistent with the format used
over D-Bus.
|
|
|
|
|
| |
This is a place holder until the code is ported to use shared API so it
can be shared by android and D-Bus daemon.
|
|
|
|
|
|
|
| |
/gobex/test_header_encode_connid test name was duplicated.
This results in Glib assert:
(unit/test-gobex-header:15356): GLib-ERROR **: duplicate test
case path: /gobex/test_header_encode_connid
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following memory leak is causes if not all interfaces are freed
once closing the connecting:
7,738 (232 direct, 7,506 indirect) bytes in 1 blocks are definitely lost in loss record 302 of 302
at 0x4C2A9C7: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x519517F: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x519EF8E: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x519F462: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x5193419: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x517E6AE: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x517A06B: ??? (in /usr/lib64/libdbus-1.so.3.8.13)
by 0x4076B9: g_dbus_setup_private (mainloop.c:314)
by 0x404B8C: client_force_disconnect (test-gdbus-client.c:882)
by 0x410B52: run_callback (tester.c:417)
by 0x4E7EA89: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.4400.1)
by 0x4E7EE1F: ??? (in /usr/lib64/libglib-2.0.so.0.4400.1)
|
|
|
|
|
| |
/TP/GAW/CL/BI-23-C/auto is similar to /TP/GAW/CL/BI-23-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAW/CL/BI-18-C/auto is similar to /TP/GAW/CL/BI-18-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAW/CL/BI-05-C/auto is similar to /TP/GAW/CL/BI-05-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAR/CL/BI-32-C/auto is similar to /TP/GAR/CL/BI-32-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAR/CL/BI-26-C/auto is similar to /TP/GAR/CL/BI-26-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAR/CL/BI-21-C/auto is similar to /TP/GAR/CL/BI-21-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAR/CL/BI-16-C/auto is similar to /TP/GAR/CL/BI-16-C but
automatically elevates the security level and retry.
|
|
|
|
|
| |
/TP/GAR/CL/BI-04-C/auto is similar to TP/GAR/CL/BI-04-C but automatically
elevates the security level and retry.
|
|
|
|
|
| |
If the test don't expect any errors to happen use set security to auto so
bt_att will take care of elevating the security whenever needed.
|
|
|
|
|
| |
The response should be Read Blob Reponse 0x0d not 0x0b which is Read
Response.
|
|
|
|
|
| |
The response should be Read Blob Reponse 0x0d not 0x0b which is Read
Response.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the issues with CSRK tests ext_signed flag has been added to
allow android/gatt handle signed write operations.
This patch fixes following tests:
GAP__TC_SEC_CSIGN_BV_02_C
GAP__TC_SEC_CSIGN_BI_01_C
GAP__TC_SEC_CSIGN_BI_02_C
GAP__TC_SEC_CSIGN_BI_03_C
GAP__TC_SEC_CSIGN_BI_04_C
SM__TC_SIGN_BV_03_C
|
|
|
|
|
| |
This will make all gdbus tests be ignored if D-Bus is not available and
one cannot be created with dbus-run-session.
|
| |
|
|
|
|
|
| |
This defines security level at ATT level so it is not necessary to use
transport specific defines.
|
|
|
|
|
| |
In case D-Bus fails to launch make the test fails so it does not hang
other tests.
|
|
|
|
|
|
| |
This adds test for uir-beacon define bellow:
https://github.com/google/uribeacon/blob/master/specification/AdvertisingMode.md
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Characteristic
Value Reliable Write procedure fails due to insufficient encryption
key size.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Characteristic
Value Reliable Write procedure fails due to insufficient authentication.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Characteristic
Value Reliable Write procedure fails due to insufficient authorization.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Characteristic
Value Reliable Write procedure fails due to write not permitted.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Characteristic
Value Reliable Write procedure fails due to invalid handle.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can reliably write
a characteristic selected by handle.
|
|
|
|
|
|
| |
In this callback params vary depending on code. Passing those as void*
allows to avoid extra memcpy that would be otherwise needed to
avoid warnings due to increased alignment when casting.
|
|
|
|
|
| |
This adds a test for Gigaset G-tag advertisement and prints manufacturer
specific data.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When creating a proxy manually with g_dbus_proxy_new it has to be freed
with g_dbus_proxy_unref otherwise it leaks:
395 (80 direct, 315 indirect) bytes in 1 blocks are definitely lost in loss record 800 of 834
at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4E84575: g_try_malloc0 (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x40E244: proxy_new (client.c:411)
by 0x40F7FD: g_dbus_proxy_new (client.c:485)
by 0x405844: client_no_object_manager (test-gdbus-client.c:837)
by 0x410882: run_callback (tester.c:413)
by 0x4E7E7FA: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x4E7EB97: ??? (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x4E7EEC1: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x411CF1: tester_run (tester.c:831)
by 0x4045E1: main (test-gdbus-client.c:986)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes leaking DBusConnection created by client_force_disconnect
causing the following trace:
40 bytes in 1 blocks are definitely lost in loss record 501 of 839
at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x519D9E1: ??? (in /usr/lib64/libdbus-1.so.3.8.11)
by 0x5191F94: ??? (in /usr/lib64/libdbus-1.so.3.8.11)
by 0x517AC1A: ??? (in /usr/lib64/libdbus-1.so.3.8.11)
by 0x517D754: ??? (in /usr/lib64/libdbus-1.so.3.8.11)
by 0x51790FB: ??? (in /usr/lib64/libdbus-1.so.3.8.11)
by 0x407739: g_dbus_setup_private (mainloop.c:314)
by 0x404ECC: client_force_disconnect (test-gdbus-client.c:879)
by 0x4108B2: run_callback (tester.c:413)
by 0x4E7E7FA: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x4E7EB97: ??? (in /usr/lib64/libglib-2.0.so.0.4200.2)
by 0x4E7EEC1: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.4200.2)
|
|
|
|
|
|
| |
This test creates a second connection without using the one created by
create_context and doesn't disconnect making test client_force_disconnect
fail.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Descriptor procedure fails due to insufficient
encryption key size.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Descriptor procedure fails due to insufficient
authentication.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Descriptor procedure fails due to insufficient
authorization.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Descriptor procedure fails due to write not
permitted.
|