Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
This change unifies the documentation comment syntax, fixes a few bad
documentation comments and completes documentation where it was missing.
|
|
This changes the typedef logic slightly for the public headers in order
for doxygen to correctly pickup and enable the client struct documentation.
|
|
|
|
|
|
This brings back the automatic pairing feature if not yet paired.
[#111 state:resolved]
|
|
|
|
This error is returned if the service does not exist on the device.
It comes handy to detect if for instance the AFC2 service is actually
setup on a device or not.
|
|
|
|
Implementations can now supply a full pair record and thus use their
own preferred method of managing pairing records if needed.
|
|
|
|
|
|
This introduces a new debug_info macro which automatically prints
the calling function, file and line number information instead of
having that information passed to every old log_debug_msg call.
|
|
|
|
|
|
This splits out SSL code and allows implementations to manually handle
session start and stop if needed. Also brings the API closer to the
lockdown request protocol.
|
|
|
|
The lockdown constructor was doing more than needed. Pairing and session
negotiation is now handled by lockdownd_client_new_with_handshake().
|
|
|
|
|
|
|
|
Apparently this is needed for every connection in order to ensure the
lockdown value for TrustedHostAttached is true. In effect, this makes
the device expose more functionality.
|
|
|
|
|
|
|
|
[#101 state:resolved]
The first pairing fails if a user has a password set on the device.
|
|
Passing the right activiation record allows activating a phone using
this functionality.
|
|
|
|
|
|
|
|
This function allows the current host (or the host specified by the
given HostID to become the trusted host of the device.
[#89 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
When NULL is given as HostID, lockdownd_pair() will use the HostID
available from userprefs.
|
|
When accessing/storing key info with userprefs, a device uuid is
required that makes it possible to distinguish between different
devices. On execution of lockdownd_client_new, the uuid is queried
via lockdown and now stored in the client struct for later reuse.
This patch also removes the uuid parameter from lockdownd_pair().
|
|
This fixes a bug where lockdown_check_result() might return -1
and lockdownd_pair() still returns success.
Thanks to dborca for spotting this.
|
|
This will change session_id out of the lockdownd_client_int struct
to a pointer instead of using a buffer of fixed size. The session_id is
allocated anyway by libplist when reading it from the plist received
from the device, so why don't just use it?
[#94 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
This removes the session_id parameter from lockdownd_stop_session
because the session_id is stored in the lockdownd_client_int structure
anyway.
|
|
This is required if the device does not send the EnableSessionSSL:true
key-value pair in the answer to the StartSession request.
[#92 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
[#87 state:resolved]
|
|
gnutls_session_t is already a pointer, we don't need to manipulate a
gnutls_session_t*
[#87 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
|
|
[#77 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
Signed-off-by: Matt Colyer <matt@colyer.name>
[#77 state:resolved]
|
|
|
|
Valgrind complains:
==2678== Conditional jump or move depends on uninitialised value(s)
==2678== at 0x3ACD40646C: lockdownd_client_new (lockdown.c:662)
==2678== by 0x405BA6: g_vfs_afc_volume_new (afc-volume.c:113)
==2678== by 0x406541: g_vfs_afc_monitor_device_added (afc-volume-monitor.c:46)
==2678== by 0x4066B1: g_vfs_afc_volume_monitor_constructor (afc-volume-monitor.c:173)
==2678== by 0x3A7FE11A38: g_object_newv (in /lib64/libgobject-2.0.so.0.2000.4)
==2678== by 0x3A7FE12584: g_object_new_valist (in /lib64/libgobject-2.0.so.0.2000.4)
==2678== by 0x3A7FE126DB: g_object_new (in /lib64/libgobject-2.0.so.0.2000.4)
==2678== by 0x408AD5: monitor_try_create (gvfsproxyvolumemonitordaemon.c:1651)
==2678== by 0x408C20: g_vfs_proxy_volume_monitor_daemon_main (gvfsproxyvolumemonitordaemon.c:1694)
==2678== by 0x37E881EA2C: (below main) (in /lib64/libc-2.10.1.so)
==2678== Uninitialised value was created by a stack allocation
==2678== at 0x405B00: g_vfs_afc_volume_new (afc-volume.c:138)
|
|
[#60 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
|
|
|
|
|