Age | Commit message (Collapse) | Author | Files | Lines |
|
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 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().
|
|
|
|
[#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 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 removes the session_id parameter from lockdownd_stop_session
because the session_id is stored in the lockdownd_client_int structure
anyway.
|
|
|
|
|
|
|
|
|
|
|