Brutta notizia dal mondo del Jailbreak.
Saurik, creatore di Cydia, ha comunicato che a causa di un errore i certificati SHSH di iOS 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1 e 6.1.2 sono andati persi. Dunque sarà come se non fossero mai stati salvati. Adesso se volessimo aggiornare il nostro dispositivo, mantenendo la possibilità di fare il Jailbreak, non possiamo in quanto senza SHSH possiamo aggiornare solamente ad iOS 6.1.3, non compatibile col JB.
Ecco il comunicato di Saurik:
Normally, I get to write articles (or give talks, or leave many-page long comments on various websites and forums) on interesting aspects of technology, confusing aspects of business, protocols and the people who standardized them, or new tools that I’ve been working on; writing these articles can be grueling at times, but at some level the task is not just rewarding, but fun.Saurik per evitare problemi in futuro ha aperto una sezione su Cydia (TSS center) dove potremo salvare manualmente i certificati SHSH.
Sadly, that is not why I have been working on this article: instead, I am here to be the bearer of bad news that will likely cause me to get a ton of hatemail. Specifically, I am writing this to tell everyone that the TSS data Cydia saved for iOS 6.0-6.1.2 is unusable. I’m also going to attempt to explain some background on the process, what the mistake was, and what users can now do instead.
In the process, I am going to explain a few parts of the iOS software security mechanism that I have not seen described often outside of technical presentations at security conferences. Additionally, I will summarize, from the perspective of a user, what is currently possible with cached APTicket information (something I actually did not know much about before writing this).
My goal is that by the end of this article readers will understand enough of the process to appreciate the mistake, the history of the issue, and why it was never caught. Additionally, it will hopefully be slightly more clear when cached APTicket information is usable (as it turns out that cached APTickets have a rather narrow range of uses) and how affected users might still be able to get this data.
Saurik ci dice anche che il problema potrebbe non presentarsi in dispositivi con processore pre-A4, affetti dal bug Limera1n (iPhone 3GS, iPhone 4, iPod 4)
[fonte]

Nessun commento :
Posta un commento
Nota. Solo i membri di questo blog possono postare un commento.