Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
plist_dict_get_item()
|
|
This should be more accurate than guessing based on what is in the
build identity and avoid doing unexpected things for unknown hardware.
|
|
|
|
|
|
|
|
|
|
to add digest for Trusted items.
|
|
|
|
|
|
|
|
The corresponding message was also "This device isn't eligible for the
requested build" with this status code.
|
|
|
|
|
|
|
|
and sound less harmful
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Martin Szulecki <m.szulecki@libimobiledevice.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
After a while, Apple's servers have been begun redirecting to a 404 page
using a 302 security redirect HTTP status code. By using a secure HTTPS
connection retrieving TSS requests started to work fine again.
|
|
It appears the number of HTTP requests from one IP to the TSS signing
servers is limited by each signing host. This workaround increases the
volume of devices that can be processed due to falling back to another
signing host in case request limiting is in effect by the original host.
|