In the news this week is something extremely relevant to last week’s discussion on nanofactory regulation - on Monday IBM announced a computer security technology that encrypts data at the hardware level, something which has been done before but apparently not to this extent. The technology is called SecureBlue. A quote from news coverage on my.freeze.com:

There are multiple ways to achieve encryption, the mathematical art of encoding data to protect it from spying eyes. Specialized software can do the trick, as can hard-wired chips inside computers.

But IBM researchers contend that unless the encryption function is performed by a computer’s central processing unit, a supremely savvy hacker can tap into the pathway between the machine’s brain and the separate encryption engine.

To guard against that, IBM is announcing Monday that it has developed “SecureBlue” a set of encryption circuitry that can be integrated into any processor, regardless of its manufacturer.

“This thing is trying to be one of the most paranoid devices on the planet,” said Charles Palmer, IBM’s head security researcher.

One of the only times data is not encrypted within a SecureBlue chip is when it is displayed on the screen. We are rapidly approaching an era where the weakest link in computer security will almost always be the user (if we aren’t there already). IBM sees the technology being used in a variety of devices from PCs to handhelds and beyond.

The encryption scheme is not computation-heavy, barely consuming any overhead. IBM seems confident that the basic security of the technology will hold even if a hacker has ways of intimately monitoring the data streams within the hardware. Presumably access to IBM’s proprietary security algorithms is the only way to crack the code - and I would expect that the details of these algorithms are only known to at most a few hundred (more likely a few dozen) people at IBM’s research labs. Even with these algorithms, it’s not certain it would even be possible to decode any given package of encrypted data because it would be associated with a long, randomized string of bits (key). Perhaps the technology has safeguards so that data can be recovered even if the keys are lost? If so, a list of keys might be kept in a centralized location managed by IBM.

SecureBlue might be seen as a complement or successor to Trusted Computing.

It is fortuitous that IBM is the source of this new security technology, as it is also the company that built the computer that almost beat the highest-rated chess player on earth (Deep Blue), the fastest computer on earth (Blue Gene), and the largest attempt at a computer simulation of the mammalian brain (Blue Brain).

Hollywood and the big business behind proprietary software will be cheering for this technology, because it gives them another way to potentially prevent consumers from copying their movies, music, software, etc. I’m cheering it on for slightly different reasons, that is, the technology’s role in protecting us from future risks associated with totally unrestricted computers and software.

Sometime in this decade or the next, there will be a revolution in desktop manufacturing. This needn’t be in the form of nanofactories - it may debut as a relatively expensive machine that uses macroscale technology to shape plastic and electronics components into toys, tools, and simple gadgets. People will eventually be able to make custom products of high quality in their own home for low cost. The revolution is already starting to happen, with machines like MIT’s “fab lab” and the MCP Realizer, among dozens of others.

When copyrighted media such as songs or video clips get duplicated and distributed, the recording and film industries take a big hit. When expensive software like AutoCAD, Quickbooks, Windows XP, Photoshop, and Maya are copied, the software industry takes a big hit.

But these might be ultimately unavoidable. Information has a tendency to run free, and if security isn’t built into the foundations of the technology, it’s futile to stop the torrent by suing people one by one.

With desktop manufacturing, it will be a different story. If the design for a hot new product becomes public knowledge, then the value of the product will plummet mere days after its release, eliminating the motivation to both invent and invest. The dangers of a malfunctioning product will potentially be duplicated millions of times over. Without hardware-level restrictions and safeguards, performing a recall on a home-fabbed product will be neigh impossible. To make things worse, copycats will attempt to create similar products that circumvent safety restrictions.

This is just the beginning of why hardware-level encryption will be so much more important in the future than today. There are large classes of both existential risk and intense global nuisance that will be facilitated by insecure computing. These include bioweapon design, missile design, cyber-terrorism, remote control of military hardware, and much more.

The single greatest long-term risk of powerful insecure computing is probably self-improving Artificial General Intelligence (AGI) that is indifferent to human welfare. As available computing power increases, it gets easier to build an intelligent computer. (How much easier we don’t know.) However, it doesn’t get any easier to build an intelligent computer that cares about humans with the same complexity and subtlety that we care about each other - a must if you’re aiming for smarter-than-human AI. To oversimplify a bit, the former is a matter of trying things out until something works, and the latter is about developing a formal theory of what an agent will do given a starting set of preferences and the ability to reprogram itself recursively. Both will take a lot of brains, but creating any AI is a problem that lends itself to brute forcing much more than creating a certain type of AI.

Before we let powerful, unrestricted computers be available to just anyone, we should solve the problem of Friendly AI. A successful solution would give us allies who actually grew up in the world of code and will have a much better idea of which types of computation are truly dangerous and which are harmless - a question which humans are ultimately unqualified to answer.