Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
[#106 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
|
|
|
|
|
|
|
|
|
|
[#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.
|
|
|
|
We don't need to maintain defaults, applications should know and
specifiy which notification ids they want to observe themselfs.
|
|
|
|
|
|
|
|
|
|
This change allows to specify the following options:
INSTPROXY_ARCHIVE_APP_ONLY - Archive only the application data
INSTPROXY_ARCHIVE_SKIP_UNINSTALL - Do not uninstall the application.
Combine these options with logical OR to specify both. These two options
combined are used by iTunes to create app archives of on-device downloaded
apps that are later copied as *.ipa files to the computer.
[#104 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
Allows enumeration, install, uninstall, upgrade, and some
other stuff with apps.
|
|
This lockdown service has been introduced in firmware 3.1 and allows to
re-arrange the Spr*ngboard icons from the computer.
[#99 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
[#96 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
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>
|
|
This makes afc_truncate look more like afc_file_truncate which is also
using uint64_t for the file size.
[#82 state:resolved]
Signed-off-by: Matt Colyer <matt@colyer.name>
|
|
This patch also adapts all corresponding internal functions.
The buffer lengths are now consistently handled as uint32_t.
|
|
This should make libiphone compatible with big endian machines.
[#85 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>
|
|
|
|
This patch removes the additional buffer that was used inside
afc_dispatch_packet. So instead of 'alloc, copy header, copy data, send,
free' it will now simply do 'send header, send data'. This should reduce
cpu usage.
|
|
|
|
trying to read a negative amount of data doesn't make much sense, and the
returned 'bytes' value will overflow if we try to do that. Just treat
negative length values as an invalid argument. An alternative way of
handling it would be to silently return OK/0 bytes read.
|
|
trying to write a negative amount of data doesn't make much sense, and bad
things will happen if we try to do that. Just treat negative length values
as an invalid argument. An alternative way of handling it would be to
silently return OK/0 bytes written.
|