Apple Vs. The FBI: Protecting The Poetry Of Code

If the FBI had succeeded in its attempt to have Apple write a new version of iOS (FBiOS, perhaps?), then what would a tech vendor have been required to do next?

Curtis Franklin Jr., Senior Editor at Dark Reading

March 31, 2016

5 Min Read
<p align="left">(Image: <a href=""target="_blank">succo</a> via Pixabay)</p>

Apple CareKit, ResearchKit: 6 Apps Aiming For A Healthier World

Apple CareKit, ResearchKit: 6 Apps Aiming For A Healthier World

Apple CareKit, ResearchKit: 6 Apps Aiming For A Healthier World (Click image for larger view and slideshow.)

The FBI says that it has cracked the iPhone in the California terrorist case. Apple says that it didn't have to write new encryption-busting software. Everyone seems to have gotten what they wanted. So, why are there still many questions bouncing around the industry?

Part of the problem is that we don't know which principles would have prevailed had the case gone to trial. The FBI dropped its charges against Apple after it determined it could get what it needed by other means. Each side claimed to be on the side of the angels, and good arguments were made by each party.

To me, though, the most compelling argument came down to whether it is right, in the US way of doing things, to force someone to write.

I am not a lawyer. I am someone who makes his living by leaning heavily on the First Amendment of the US Constitution. And certain arguments lead me to uncharitable thoughts. As an example, any argument that includes the phrase, "If it saves just one life..." makes me twitch in unattractive ways.

With all that out of the way, let's get back to the idea of the government forcing Apple (or any company) to write new software. Any software. I have a problem with the very idea, because it seems to me a Stalefish McTwist down a slippery half-pipe of government compulsion. If the FBI had succeeded in its attempt to have Apple write a new version of iOS (FBiOS, perhaps?), then what would an industry vendor have been required to do next?

The FBI's argument that this was a single case, and that no one would ever use the software or ask for anything similar again, had been proven false before the stories from the first press conference were filed. Federal prosecutors were publicly lining up to use the software (or similar legal means) to get Apple to provide paths into iPhones in dozens of cases. A sheriff in Polk County, Fla., had even promised to arrest Apple CEO Tim Cook if a prosecutor in Winter Haven, Fla., wanted iPhone info and Apple didn't comply.

With a legal precedent in place, every company that creates software that has any security feature would have been in the position of having to build a special government edition of the code, with full information-grabbing functionality included. And once those editions existed, then no operating system or application would have been secure.

My real problem isn't with the lack of security (though there are enormous issues with that). Rather, my problem is with the idea that engineers, programmers, and companies who believe in the importance of strong security might be forced to write programs that are intrinsically insecure. It would be like forcing Wordsworth to write free verse, or e.e. cummings to use the Caps Lock key on his typewriter. It would be wrong.

Gain insight into the latest threats and emerging best practices for managing them. Attend the Security Track at Interop Las Vegas, May 2-6. Register now!

Now, I can hear two arguments about this. The first is that Apple is a corporation and commercial speech has less protection under the First Amendment than does individual speech. That's quite true, though all of the precedent regarding computer software as speech has involved commercial entities as the authors. The precedents leave a bit of murk about protection, though all of them are around whether software can be forbidden -- not whether it must be written.

The second argument is that forcing e.e. cummings to write with proper capitalization might hinder his artistic expression, but it wouldn't place lives in danger. That argument is true but irrelevant. In the US, our Constitutional rights aren't suspended when an individual life (or even quite a few lives) are placed in danger. Don't believe me? I give you the Second Amendment. And the Fifth. And sections of the Fourth.

Put simply, the statement widely credited to John Adams, the second president of the US, that ours is "a government of laws, not of men" means our principles are what matter most and are what we pledge our honor to uphold. We don't promise fealty to a person or an office: We are a nation that is united by ideas and ideals.

Sooner or later, another case will come up and we'll have this argument again. I truly hope, no matter the individual case, that we remember compelling people to work against their will has never gone particularly well for us. There are other ways to solve technological problems, and better ways to preserve our safety.

I suspect that some folks reading this will have other opinions on the subject. I'd love to have a discussion about your ideas in the comments section below. I look forward to the conversation as we all exercise our rights under the First Amendment.

Read more about:


About the Author(s)

Curtis Franklin Jr.

Senior Editor at Dark Reading

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and other conferences.

Previously he was editor of Light Reading's Security Now and executive editor, technology, at InformationWeek where he was also executive producer of InformationWeek's online radio and podcast episodes.

Curtis has been writing about technologies and products in computing and networking since the early 1980s. He has contributed to a number of technology-industry publications including Enterprise Efficiency, ChannelWeb, Network Computing, InfoWorld, PCWorld, Dark Reading, and on subjects ranging from mobile enterprise computing to enterprise security and wireless networking.

Curtis is the author of thousands of articles, the co-author of five books, and has been a frequent speaker at computer and networking industry conferences across North America and Europe. His most popular book, The Absolute Beginner's Guide to Podcasting, with co-author George Colombo, was published by Que Books. His most recent book, Cloud Computing: Technologies and Strategies of the Ubiquitous Data Center, with co-author Brian Chee, was released in April 2010. His next book, Securing the Cloud: Security Strategies for the Ubiquitous Data Center, with co-author Brian Chee, is scheduled for release in the Fall of 2018.

When he's not writing, Curtis is a painter, photographer, cook, and multi-instrumentalist musician. He is active in amateur radio (KG4GWA), scuba diving, stand-up paddleboarding, and is a certified Florida Master Naturalist.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights