61–70 of 126 posts
Neat, $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.
Maybe Zerodium would've paid $75k but that would be less ethical because Israel and America would weaponize it.
Earlier 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.
And for that reason I wouldn't hassle laymen over it but among the HN crowd I expect a bit more care. An "anything goes" attitude makes communication more difficult. "Soft brick" is the correct term that already exists.
Which is the term that the article uses.
"The result is a device that’s soft-bricked, requiring a device erase and restore from backup."
Earlier 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.
Also, although HN readers probably have many devices in their homes there are people out there who have only a phone and no computer. For them this would be pretty catastrophic. Hopefully they’d take their device to Apple or a third party technician
Earlier 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.
So maybe the term shouldn't be 'soft brick' but rather 'muddied'.
"That updated muddied my device, I had to clean it up with a restore"
Earlier quoted context omitted.
“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…
Incorrect. Bricking means a device becomes a doorstop that cannot be resurrected or repaired by the user non-invasively. That's the whole point of the term.
Earlier quoted context omitted.
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.
It doesn't just force a reboot, it forces a never-ending loop of reboots, rebooting each time you reboot it. > 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.
He totally murdered that guy!
What? Why would you say murdered, he only gave him a black eye?
I know, but that's still pretty serious.
Earlier quoted context omitted.
It was actually almost 3 decades ago, making me feel extremely old - the period right at the end of '96 and into mid '97 when this was a popular way to cause mischief via IRC was truly a magical time
Hard to believe that during those times in IRC, you were used to automatically (and proudly) advertising your IP address, your exact client version, and the means for a direct connection to your client without any server in between (CTCP, literally “client-to-client protocol”). And all of that most often with no packet filter whatsoever, not even NAT, in between. Everything was plaintext, including “authentication”,…
I was behind NAT when I first got on IRC in ‘98. I set it up with ipfwadm.
Earlier quoted context omitted.
Almost like a "soft"-brick, if you would.
A soft brick would be a brick before being fired in an oven, no? So maybe the term shouldn't be 'soft brick' but rather 'muddied'. "That updated muddied my device, I had to clean it up with a restore"