Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
output
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This does not directly exit if anything breaks but attempts to read one
more message from restored which usually is a StatusMsg and contains
information about the error that occoured.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should indicate that a manual mode switch is required.
|
|
The code path without TSS request did not initialize the recovery client
in order for it to be used to send iBEC. Now the client is always initialized.
|