4 ms·
Feds move to cancel iPhone hearing
- greenyoda 11y agoThe headline now reads "Feds move to postpone iPhone hearing" instead of "cancel".
- zmanian 11y agoI'd read it as they really want to cancel but it looks better to judge to postpone now and they say later we hacked the phone ourselves or we broke the phone and now don't need Apple anymore.
- jlgaddis 11y agoNo, no, no. This NEEDS to go forward. It needs to be decided, once and for all.
- PhantomGremlin 11y agoIt needs to be decided, once and for all. That's exactly why they are delaying. They don't want the decision to go against them. The FBI is clearly abusing the All Writs Act. The decision in Apple's favor in Brooklyn spelled this out. It's very compelling reading, and I'm sure it would have influenced the California court. https://news.ycombinator.com/item?id=11199169 https://news.ycombinator.com/item?id=11199169
- jessaustin 11y agoTo look on the bright side, this obviously-bullshit maneuver still weakens FBI's position for the next round.
- fweespee_ch 11y agoI don't believe that is true unless it goes through the courts all the way. This will be forgotten without a ruling.
- pfista 11y agoCorrection: feds realise they have no chance of winning and back out to prevent a precedent that would hurt them in the future.
- cvgraham 11y agoCompletely agree. Just posted the exact same thing on a similar thread!
- gherkin0 11y agoIf the FBI is playing games with the court system, could Apple call them out on it and convince the court to rule on issues anyway?
- dogma1138 11y agoNot really, plus the first rule of law is to never ask a question you do not know the answer too. Only a suicidal lawyer would even agree to do it, they "won" why poke the bear?
- caffeineninja 11y agoIt's probably the hardware bruteforce unlock that's been floating around for about a year: Example: http://blog.mdsec.co.uk/2015/03/bruteforcing-ios-screenlock.html http://blog.mdsec.co.uk/2015/03/bruteforcing-ios-screenlock....
- camillomiller 11y agoNope, that's not working anymore since iOS 8.2
- pfg 11y agoThe article mentions the device might be exploiting CVE-2014-4451, which was fixed in iOS 8.1.1.
- dang 11y agoThe article at https://news.ycombinator.com/item?id=11332965 https://news.ycombinator.com/item?id=11332965 seems a bit more substantive and that thread is far more active, so I guess we'll treat this one as the duplicate despite its having been posted earlier.