Earlier quoted context omitted.
Wasn’t it in OS X before that?
Documentation claims 10.6, which is the equivalent OS X version (both are the 2009 releases).
How a single line of code could brick your iPhone
51–60 of 126 posts
Re: How a single line of code could brick your iPhone
#52Re: How a single line of code could brick your iPhone
#53The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
From observation, "brick" has evolved, as things do in language. In practice, it rarely means the traditional definition you refer to, but the softer one used here.
"Soft brick" is the correct term that already exists.
Re: How a single line of code could brick your iPhone
#54Earlier quoted context omitted.
From observation, "brick" has evolved, as things do in language. In practice, it rarely means the traditional definition you refer to, but the softer one used here.
Almost like a "soft"-brick, if you would.
Re: How a single line of code could brick your iPhone
#55The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
Re: How a single line of code could brick your iPhone
#56The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
More importantly, the single line only forces a reboot; even if we consider needing external fixes to be a brick, the title is still incorrect.
> The result is a device that’s soft-bricked, requiring a device erase and restore from backup.
Requiring a device erase isn't a full brick, no, but it's still pretty serious.
Re: How a single line of code could brick your iPhone
#57The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
Re: How a single line of code could brick your iPhone
#58Earlier quoted context omitted.
I read a comment under the story about the recent YouTube vulnerability where one could unmask the related Google account and its owner using the standard YouTube API (something similar to that anyway), and they explained a lot of lesser-known nuances in establishing values for bounties like these, and it helped explain a lot (not all) of the reasons for what might seem like low-ball/high-ball valuations on the surfa…
is this the one: https://news.ycombinator.com/item?id=43025038
Re: How a single line of code could brick your iPhone
#59The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.
“Bricking” isn’t a rigorously defined term, it’s more like “realtime” in the sense that it comes with an implicit “(for this particular user in this particular scenario)”. For most users a device is bricked if it doesn’t turn on and work when you press the power button. For most readers here, using dev tools to re-flash a bootloader would be fairly easy but if USB stops working it might be game over. I’m sure there a…
Re: How a single line of code could brick your iPhone
#60Neat, $17,500 is pretty good, I’m so used to these blog posts being for peanuts, or where companies fix the vulnerability but don’t pay out at all. Apple’s gotten better about this since 2019.