Slashdot Mirror
DoJ Wants Apple To Decrypt 12 More iPhones (macrumors.com)
tlhIngan writes: The Wall Street Journal (paywalled) is reporting that the Department of Justice is seeking Apple's help in decrypting 12 other iPhones that may contain crime-related evidence. The cases are not identified, though a list of the 12 phones in question has come out, but it is not known what level of Apple assistance is required (i.e., how many of those cases are waiting on the FBI request for special firmware to be developed and to be used on "one more phone"). It appears Tim Cook's assertion that hundreds of requests are waiting on this software may not be a fabrication, and the goal is not about just one phone, but to set a precedent to unlock more phones.
As TechDirt (which also lists those 12 cases, a list which certainly does not encompass all the phones the Feds would like to peer into) puts it, "[O]nce again, Director Comey was flat out lying when he claimed the FBI has no interest in setting a precedent."
"This is my surprised face."
Meanwhile: "...New York City police commissioner, William J. Bratton, and the Manhattan district attorney, Cyrus R. Vance Jr., criticized Apple after it refused to comply with the court order and said that they currently possessed 175 iPhones that they could not unlock."
So that's 188 on the list so far...
Here are a some non-paywalled links:
http://www.reuters.com/article/us-apple-encryption-idUSKCN0VW0BM
http://www.macrumors.com/2016/02/23/doj-vs-apple-12-court-orders
If the new owners of Slashdot really want to improve this site (and I have seen no evidence that they do), a good first step would be stop linking to stories that are paywalled, or that prohibit adblockers. There are always plenty of alternatives.
With increasing delays on how long you must wait to try again after about 5 failed attempts...
Depends on how long "Jest laying around is" 2 hrs and 21 mins then yes.
Depending on how long you have it you can LOCK it for a few mins and They can't use it.
TRY - wait time ---- Total Time
1-5 -- none ---------- none
6 ---- 1 minute ------ 1 minute
7 ---- 5 minutes ----- 6 minutes
8 ---- 15 minutes --- 21 minutes
9 ---- 60 minutes --- 81 minutes
10 -- 60 minutes ---141 minutes
11 -- black screen -- wiped device
Here's a link to an article showing that there's hundreds or thousands of state/local cases waiting for this exact precedent.
http://www.nytimes.com/2016/02...
To that point, the New York City police commissioner, William J. Bratton, and the Manhattan district attorney, Cyrus R. Vance Jr., criticized Apple after it refused to comply with the court order and said that they currently possessed 175 iPhones that they could not unlock.
Charlie Rose recently interviewed Mr. Vance and asked if he would want access to all phones that were part of a criminal proceeding should the government prevail in the San Bernardino case.
Mr. Vance responded: “Absolutely right.”
There are two types of people in the world: Those who crave closure
Ummm...I've seen you here for a very long time, and with such a low UID, you've been here a while... have you never used the Submission system before to know how it works? You know, the community user (not an editor) goes out on the internet, finds an article that he thinks would be good for the site, posts a summary with (hopefully) a link... and then the "editors" (I wonder how much of the firehose acceptance procedure is automated, given the amount of times I've seen early stories have had broken links that had to be, and eventually were, fixed) will pull that submission in to display on the front page.
Judging by the fact that your MacRumors link seems to have been added to the summary and noted as the primary link in the headline; as well as a link to techdirt added post user quoted summary...I think it's safe to say that the human editors have gone back and added some of the more open links that you've suggested, albeit keeping the original user submitted WSJ link. Already that's marginally better than how it used to be with direct copy and only an edit if a story /summary posted was wildly inaccurate...and often not even then.
How fast do you really expect this site to change under new ownership, anyway? We've already made our distaste for overwhelming change very much heard with the previous masters (slashdot beta...yes, it was a bad design...but boy did we as a community let them know how we felt about it). I frankly don't blame Whipslash & team from taking their time with deciding on what changes to start implementing. They even devoted a full article/discussion to getting community opinions on the matter. They know we're the sort that run for the pitchforks and torches whenever something is slightly amiss (you can put yours down for the moment...seriously), and they're not going to want to upset that balance for fear of revolt or (worse for them) mass exodus.
In summary: The new /. team is going to need at least a few months to get the new code worked out and I wouldn't be surprised if it's all going to be stuff that we as a community wouldn't even notice unless we were completely focused on the subtle. As a WebDev rolling out a new site for my company, it took us over a year of planning and 6 months of coding to get things to where a completely fresh new site was rolled out (granted...as a software house, we move slower than what appears to be the norm). All the back end automation stuff is probably going to be streamlined and fluffed to serve the new masters before we start to see ANYTHING on the front end.
When the news broke it was originally reported by only the WSJ so we wanted to provide the breaking news before waiting for another site to regurgitate the news. Once they did, we updated the story (which was submitted to us by a user and voted up in the firehose).
No evidence that we want to improve the site huh? Well I answered hundreds of questions here on how we can improve Slashdot: https://ask.slashdot.org/story...
In the 3 weeks we have owned the site we have removed the "Jobs" section, discontinued "Videos" (by popular demand), fixed the search bar, have the groundwork laid to roll out https in the next week or two, and are well on our way to supporting Unicode.