The Law Is Clear: the FBI Cannot Make Apple Rewrite Its OS (backchannel.com)

An anonymous reader cites a post by Susan Crawford, Harvard Law Professor and former Obama Special Assistant: From her column at Backchannel, "Barack Obama has a fine legal mind. But he may not have been using it when he talked about encryption last week. [...] The problem for the president is that when it comes to the specific battle going on right now between Apple and the FBI, the law is clear: twenty years ago, Congress passed a statute, the Communications Assistance for Law Enforcement Act (CALEA) that does not allow the government to tell manufacturers how to design or configure a phone or software used by that phone -- including security software used by that phone.

Comments

Good to hear.

[jellomizer]

The problem with this whole debate, is assuming making a system that is secure is beyond the means of mortal men. And will need a big organization to make such a system.

The truth is. If Apple are shown to be insecure, the bad guys will not use apple, they may make their own OS, which doesn't have the back doors. It may not be a fancy but secure for what is needed.

So Apple is loosing business, and the bad guys are still going under the radar.

Re:Good to hear.

[Anonymous Coward]

For all the disappointments the Obama administration has brought, the most disappointing has been its lawlessness.

Let's address this claim one point at a time.

Re-writing laws through the EPA,

The *laws* in question specifically delegate the creation of the regulations *to* the EPA. They are acting *fully* within the bounds of those laws when they create their regulations.

refusing to enforce others,

The Executive has *always* had discretion on how to allocate its resources for enforcement of the law. This is true at the federal, state, and local level, and always has been.

using EOs as a fig leaf for outright lawbreaking,

Executive Orders are legal. That is a long-established fact. They cannot change the law, nor have any of his EOs purported to do so. Additionally, he's used *fewer* EOs (per term) than any of his predecessors back as far as Grover Cleveland.

re-writing Obamacare on the fly as if there were no separation of powers at all...

There was no 're-writing' of Obama care. This is just a duplicate of the prior two, and equally empty. He has, as he is legally empowered to do, declined to enforce certain aspects of the law (pertaining to the timeline by which small businesses must comply with those certain aspects of the law), thereby preventing fines and penalties being levied on innocent actors simply because they were unable to adjust their business practices and software (at the mercy of third parties) to comply with a new law in the initial timeline. This is (again) a *COMMON* occurrence at the Federal, State, and local levels, because sane people don't want good actors penalized for things beyond their control, or for failing while acting in good faith.

Re:Barack "Executive Order" Obama...

[Zak3056]

I'm not jumping into the middle of this fight (I'm not educated enough on the subject) but I will say that there is nothing inherently wrong with an executive order. Many laws that congress writes delegate various powers to the executive--this is why we have a Code of Federal Regulations to go along with US code (USC enables the executive branch to do something, and the CFR is the details of that something... at least in theory). An executive order is a reasonable way for the President (the head of the executive branch) to direct HOW the executive branch does something. The problem arises when executive orders purport to enable or forbid something the executive branch has no power to enable or forbid.

Simply counting how many executive orders a president issues is meaningless in a vacuum. One has to actually ANALYZE those orders to determine if "screw the laws and precedents" is accurate with regard to a particular president.