EMPLOYEE CARL AUSTIN TERMINATED FOR INAPPROPRIATE CONDUCT. 1 page

From that day on, nobody messed with her; Susan Fletcher was Commander Strathmore’s golden girl.

But Strathmore’s young cryptographers were not the only ones who learned to respect him; early in his career Strathmore made his presence known to his superiors by proposing a number of unorthodox and highly successful intelligence operations. As he moved up the ranks, Trevor Strathmore became known for his cogent, reductive analyses of highly complex situations. He seemed to have an uncanny ability to see past the moral perplexities surrounding the NSA’s difficult decisions and to act without remorse in the interest of the common good.

There was no doubt in anyone’s mind that Strathmore loved his country. He was known to his colleagues as a patriot and a visionary . . . a decent man in a world of lies.

In the years since Susan’s arrival at the NSA, Strathmore had skyrocketed from head of Crypto Development to second‑in‑command of the entire NSA. Now only one man outranked Commander Strathmore there‑Director Leland Fontaine, the mythical overlord of the Puzzle Palace‑never seen, occasionally heard, and eternally feared. He and Strathmore seldom saw eye to eye, and when they met, it was like the clash of the titans. Fontaine was a giant among giants, but Strathmore didn’t seem to care. He argued his ideas to the director with all the restraint of an impassioned boxer. Not even the President of the United States dared challenge Fontaine the way Strathmore did. One needed political immunity to do that‑or, in Strathmore’s case, political indifference.

* * *

Susan arrived at the top of the stairs. Before she could knock, Strathmore’s electronic door lock buzzed. The door swung open, and the commander waved her in.

“Thanks for coming, Susan. I owe you one.”

“Not at all.” She smiled as she sat opposite his desk.

Strathmore was a rangy, thick‑fleshed man whose muted features somehow disguised his hard‑nosed efficiency and demand for perfection. His gray eyes usually suggested a confidence and discretion born from experience, but today they looked wild and unsettled.

“You look beat,” Susan said.

“I’ve been better.” Strathmore sighed.

I’ll say, she thought.

Strathmore looked as bad as Susan had ever seen him. His thinning gray hair was disheveled, and even in the room’s crisp air‑conditioning, his forehead was beaded with sweat. He looked like he’d slept in his suit. He was sitting behind a modern desk with two recessed keypads and a computer monitor at one end. It was strewn with computer printouts and looked like some sort of alien cockpit propped there in the center of his curtained chamber.

“Tough week?” she inquired.

Strathmore shrugged. “The usual. The EFF’s all over me about civilian privacy rights again.”

Susan chuckled. The EFF, or Electronics Frontier Foundation, was a worldwide coalition of computer users who had founded a powerful civil liberties coalition aimed at supporting free speech on‑line and educating others to the realities and dangers of living in an electronic world. They were constantly lobbying against what they called “the Orwellian eavesdropping capabilities of government agencies"‑particularly the NSA. The EFF was a perpetual thorn in Strathmore’s side.

“Sounds like business as usual,” she said. “So what’s this big emergency you got me out of the tub for?”

Strathmore sat a moment, absently fingering the computer trackball embedded in his desktop. After a long silence, he caught Susan’s gaze and held it. “What’s the longest you’ve ever seen TRANSLTR take to break a code?”

The question caught Susan entirely off guard. It seemed meaningless. This is what he called me in for?

“Well . . .” She hesitated. “We hit a COMINT intercept a few months ago that took about an hour, but it had a ridiculously long key‑ten thousand bits or something like that.”

Strathmore grunted. “An hour, huh? What about some of the boundary probes we’ve run?”

Susan shrugged. “Well, if you include diagnostics, it’s obviously longer.”

“How much longer?”

Susan couldn’t imagine what Strathmore was getting at. “Well, sir, I tried an algorithm last March with a segmented million‑bit key. Illegal looping functions, cellular automata, the works. TRANSLTR still broke it.”

“How long?”

“Three hours.”

Strathmore arched his eyebrows. “Three hours? That long?”

Susan frowned, mildly offended. Her job for the last three years had been to fine‑tune the most secret computer in the world; most of the programming that made TRANSLTR so fast was hers. A million‑bit key was hardly a realistic scenario.

“Okay,” Strathmore said. “So even in extreme conditions, the longest a code has ever survived inside TRANSLTR is about three hours?”

Susan nodded. “Yeah. More or less.”

Strathmore paused as if afraid to say something he might regret. Finally he looked up. “TRANSLTR’s hit something . . .” He stopped.

Susan waited. “More than three hours?”

Strathmore nodded.

She looked unconcerned. “A new diagnostic? Something from the Sys‑Sec Department?”

Strathmore shook his head. “It’s an outside file.”

Susan waited for the punch line, but it never came. “An outside file? You’re joking, right?”

“I wish. I queued it last night around eleven thirty. It hasn’t broken yet.”

Susan’s jaw dropped. She looked at her watch and then back at Strathmore. “It’s still going? Over fifteen hours?”

Strathmore leaned forward and rotated his monitor toward Susan. The screen was black except for a small, yellow text box blinking in the middle.

TIME ELAPSED: 15:09:33

AWAITING KEY: ________

Susan stared in amazement. It appeared TRANSLTR had been working on one code for over fifteen hours. She knew the computer’s processors auditioned thirty million keys per second‑one hundred billion per hour. If TRANSLTR was still counting, that meant the key had to be enormous‑over ten billion digits long. It was absolute insanity.

“It’s impossible!” she declared. “Have you checked for error flags? Maybe TRANSLTR hit a glitch and—”

“The run’s clean.”

“But the pass‑key must be huge!”

Strathmore shook his head. “Standard commercial algorithm. I’m guessing a sixty‑four‑bit key.”

Mystified, Susan looked out the window at TRANSLTR below. She knew from experience that it could locate a sixty‑four‑bit key in under ten minutes. “There’s got to be some explanation.”

Strathmore nodded. “There is. You’re not going to like it.”

Susan looked uneasy. “Is TRANSLTR malfunctioning?”

“TRANSLTR’s fine.”

“Have we got a virus?”

Strathmore shook his head. “No virus. Just hear me out.”

Susan was flabbergasted. TRANSLTR had never hit a code it couldn’t break in under an hour. Usually the cleartext was delivered to Strathmore’s printout module within minutes. She glanced at the high‑speed printer behind his desk. It was empty.

“Susan,” Strathmore said quietly. “This is going to be hard to accept at first, but just listen a minute.” He chewed his lip. “This code that TRANSLTR’s working on‑it’s unique. It’s like nothing we’ve ever seen before.” Strathmore paused, as if the words were hard for him to say. “This code is unbreakable.”

Susan stared at him and almost laughed. Unbreakable? What was THAT supposed to mean? There was no such thing as an unbreakable code‑some took longer than others, but every code was breakable. It was mathematically guaranteed that sooner or later TRANSLTR would guess the right key. “I beg your pardon?”

“The code’s unbreakable,” he repeated flatly.

Unbreakable? Susan couldn’t believe the word had been uttered by a man with twenty‑seven years of code analysis experience.

“Unbreakable, sir?” she said uneasily. “What about the Bergofsky Principle?”

Susan had learned about the Bergofsky Principle early in her career. It was a cornerstone of brute‑force technology. It was also Strathmore’s inspiration for building TRANSLTR. The principle clearly stated that if a computer tried enough keys, it was mathematically guaranteed to find the right one. A code’s security was not that its pass‑key was unfindable but rather that most people didn’t have the time or equipment to try.

Strathmore shook his head. “This code’s different.”

“Different?” Susan eyed him askance. An unbreakable code is a mathematical impossibility! He knows that!

Strathmore ran a hand across his sweaty scalp. “This code is the product of a brand‑new encryption algorithm‑one we’ve never seen before.”

Now Susan was even more doubtful. Encryption algorithms were just mathematical formulas, recipes for scrambling text into code. Mathematicians and programmers created new algorithms every day. There were hundreds of them on the market‑PGP, Diffie‑Hellman, ZIP, IDEA, El Gamal. TRANSLTR broke all of their codes every day, no problem. To TRANSLTR all codes looked identical, regardless of which algorithm wrote them.

“I don’t understand,” she argued. “We’re not talking about reverse‑engineering some complex function, we’re talking brute force. PGP, Lucifer, DSA‑it doesn’t matter. The algorithm generates a key it thinks is secure, and TRANSLTR keeps guessing until it finds it.”

Strathmore’s reply had the controlled patience of a good teacher. “Yes, Susan, TRANSLTR will always find the key‑even if it’s huge.” He paused a long moment. “Unless . . .”

Susan wanted to speak, but it was clear Strathmore was about to drop his bomb. Unless what?

“Unless the computer doesn’t know when it’s broken the code.”

Susan almost fell out of her chair. “What!”

“Unless the computer guesses the correct key but just keeps guessing because it doesn’t realize it found the right key.” Strathmore looked bleak. “I think this algorithm has got a rotating cleartext.”

Susan gaped.

The notion of a rotating cleartext function was first put forth in an obscure, 1987 paper by a Hungarian mathematician, Josef Harne. Because brute‑force computers broke codes by examining cleartext for identifiable word patterns, Harne proposed an encryption algorithm that, in addition to encrypting, shifted decrypted cleartext over a time variant. In theory, the perpetual mutation would ensure that the attacking computer would never locate recognizable word patterns and thus never know when it had found the proper key. The concept was somewhat like the idea of colonizing Mars‑fathomable on an intellectual level, but, at present, well beyond human ability.

“Where did you get this thing?” she demanded.

The commander’s response was slow. “A public sector programmer wrote it.”

“What?” Susan collapsed back in her chair. “We’ve got the best programmers in the world downstairs! All of us working together have never even come close to writing a rotating cleartext function. Are you trying to tell me some punk with a PC figured out how to do it?”

Strathmore lowered his voice in an apparent effort to calm her. “I wouldn’t call this guy a punk.”

Susan wasn’t listening. She was convinced there had to be some other explanation: A glitch. A virus. Anything was more likely than an unbreakable code.

Strathmore eyed her sternly. “One of the most brilliant cryptographic minds of all time wrote this algorithm.”

Susan was more doubtful than ever; the most brilliant cryptographic minds of all time were in her department, and she certainly would have heard about an algorithm like this.

“Who?” she demanded.

“I’m sure you can guess.” Strathmore said. “He’s not too fond of the NSA.”

“Well, that narrows it down!” she snapped sarcastically.

“He worked on the TRANSLTR project. He broke the rules. Almost caused an intelligence nightmare. I deported him.”

Susan’s face was blank only an instant before going white. “Oh my God . . .”

Strathmore nodded. “He’s been bragging all year about his work on a brute‑force‑resistant algorithm.”

“B‑but . . .” Susan stammered. “I thought he was bluffing. He actually did it?”

“He did. The ultimate unbreakable code‑writer.”

Susan was silent a long moment. “But . . . that means . . .”

Strathmore looked her dead in the eye. “Yes. Ensei Tankado just made TRANSLTR obsolete.”

CHAPTER 6

Although Ensei Tankado was not alive during the Second World War, he carefully studied everything about it‑particularly about its culminating event, the blast in which 100,000 of his countrymen where incinerated by an atomic bomb.

Hiroshima, 8:15 a.m. August 6, 1945‑a vile act of destruction. A senseless display of power by a country that had already won the war. Tankado had accepted all that. But what he could never accept was that the bomb had robbed him of ever knowing his mother. She had died giving birth to him‑complications brought on by the radiation poisoning she’d suffered so many years earlier.

In 1945, before Ensei was born, his mother, like many of her friends, traveled to Hiroshima to volunteer in the burn centers. It was there that she became one of the hibakusha‑the radiated people. Nineteen years later, at the age of thirty‑six, as she lay in the delivery room bleeding internally, she knew she was finally going to die. What she did not know was that death would spare her the final horror‑her only child was to be born deformed.

Ensei’s father never even saw his son. Bewildered by the loss of his wife and shamed by the arrival of what the nurses told him was an imperfect child who probably would not survive the night, he disappeared from the hospital and never came back. Ensei Tankado was placed in a foster home.

Every night the young Tankado stared down at the twisted fingers holding his daruma wish‑doll and swore he’d have revenge‑revenge against the country that had stolen his mother and shamed his father into abandoning him. What he didn’t know was that destiny was about to intervene.

In February of Ensei’s twelfth year, a computer manufacturer in Tokyo called his foster family and asked if their crippled child might take part in a test group for a new keyboard they’d developed for handicapped children. His family agreed.

Although Ensei Tankado had never seen a computer, it seemed he instinctively knew how to use it. The computer opened worlds he had never imagined possible. Before long it became his entire life. As he got older, he gave classes, earned money, and eventually earned a scholarship to Doshisha University. Soon Ensei Tankado was known across Tokyo as fugusha kisai‑the crippled genius.

Tankado eventually read about Pearl Harbor and Japanese war crimes. His hatred of America slowly faded. He became a devout Buddhist. He forgot his childhood vow of revenge; forgiveness was the only path to enlightenment.

By the time he was twenty, Ensei Tankado was somewhat of an underground cult figure among programmers. IBM offered him a work visa and a post in Texas. Tankado jumped at the chance. Three years later he had left IBM, was living in New York, and was writing software on his own. He rode the new wave of public‑key encryption. He wrote algorithms and made a fortune.

Like many of the top authors of encryption algorithms, Tankado was courted by the NSA. The irony was not lost on him‑the opportunity to work in the heart of the government in a country he had once vowed to hate. He decided to go on the interview. Whatever doubts he had disappeared when he met Commander Strathmore. They talked frankly about Tankado’s background, the potential hostility he might feel toward the U.S . . . his plans for the future. Tankado took a polygraph test and underwent five weeks of rigorous psychological profiles. He passed them all. His hatred had been replaced by his devotion to Buddha. Four months later Ensei Tankado went to work in the Cryptography Department of the National Security Agency.

Despite his large salary, Tankado went to work on an old Moped and ate a bag lunch alone at his desk instead of joining the rest of the department for prime rib and vichyssoise in the commissary. The other cryptographers revered him. He was brilliant‑as creative a programmer as any of them had ever seen. He was kind and honest, quiet, and of impeccable ethics. Moral integrity was of paramount importance to him. It was for this reason that his dismissal from the NSA and subsequent deportation had been such a shock.

* * *

Tankado, like the rest of the Crypto staff, had been working on the TRANSLTR project with the understanding that if successful, it would be used to decipher E‑mail only in cases pre‑approved by the Justice Department. The NSA’s use of TRANSLTR was to be regulated in much the same way the FBI needed a federal court order to install a wiretap. TRANSLTR was to include programming that called for passwords held in escrow by the Federal Reserve and the Justice Department in order to decipher a file. This would prevent the NSA from listening indiscriminately to the personal communications of law‑abiding citizens around the globe.

However, when the time came to enter that programming, the TRANSLTR staff was told there had been a change of plans. Because of the time pressures often associated with the NSA’s anti‑terrorist work, TRANSLTR was to be a free‑standing decryption device whose day‑to‑day operation would be regulated solely by the NSA.

Ensei Tankado was outraged. This meant the NSA would, in effect, be able to open everyone’s mail and reseal it without their knowing. It was like having a bug in every phone in the world. Strathmore attempted to make Tankado see TRANSLTR as a law‑enforcement device, but it was no use; Tankado was adamant that it constituted a gross violation of human rights. He quit on the spot and within hours violated the NSA’s code of secrecy by trying to contact the Electronic Frontier Foundation. Tankado stood poised to shock the world with his story of a secret machine capable of exposing computer users around the world to unthinkable government treachery. The NSA had had no choice but to stop him.

Tankado’s capture and deportation, widely publicized among on‑line newsgroups, had been an unfortunate public shaming. Against Strathmore’s wishes, the NSA damage‑control specialists‑nervous that Tankado would try to convince people of TRANSLTR’s existence‑generated rumors that destroyed his credibility. Ensei Tankado was shunned by the global computer community‑nobody trusted a cripple accused of spying, particularly when he was trying to buy his freedom with absurd allegations about a U.S. code‑breaking machine.

The oddest thing of all was that Tankado seemed to understand; it was all part of the intelligence game. He appeared to harbor no anger, only resolve. As security escorted him away, Tankado spoke his final words to Strathmore with a chilling calm.

“We all have a right to keep secrets,” he’d said. “Someday I’ll see to it we can.”

CHAPTER 7

Susan’s mind was racing‑Ensei Tankado wrote a program that creates unbreakable codes! She could barely grasp the thought.

“Digital Fortress,” Strathmore said. “That’s what he’s calling it. It’s the ultimate counterintelligence weapon. If this program hits the market, every third grader with a modem will be able to send codes the NSA can’t break. Our intelligence will be shot.”

But Susan’s thoughts were far removed from the political implications of Digital Fortress. She was still struggling to comprehend its existence. She’d spent her life breaking codes, firmly denying the existence of the ultimate code. Every code is breakable‑the Bergofsky Principle! She felt like an atheist coming face to face with God.

“If this code gets out,” she whispered, “cryptography will become a dead science.”

Strathmore nodded. “That’s the least of our problems.”

“Can we pay Tankado off? I know he hates us, but can’t we offer him a few million dollars? Convince him not to distribute?”

Strathmore laughed. “A few million? Do you know what this thing is worth? Every government in the world will bid top dollar. Can you imagine telling the President that we’re still cable‑snooping the Iraqis but we can’t read the intercepts anymore? This isn’t just about the NSA, it’s about the entire intelligence community. This facility provides support for everyone‑the FBI, CIA, DEA; they’d all be flying blind. The drug cartels’ shipments would become untraceable, major corporations could transfer money with no paper trail and leave the IRS out in the cold, terrorists could chat in total secrecy‑it would be chaos.”

“The EFF will have field day,” Susan said, pale.

“The EFF doesn’t have the first clue about what we do here,” Strathmore railed in disgust. “If they knew how many terrorist attacks we’ve stopped because we can decrypt codes, they’d change their tune.”

Susan agreed, but she also knew the realities; the EFF would never know how important TRANSLTR was. TRANSLTR had helped foil dozens of attacks, but the information was highly classified and would never be released. The rationale behind the secrecy was simple: The government could not afford the mass hysteria caused by revealing the truth; no one knew how the public would react to the news that there had been two nuclear close calls by fundamentalist groups on U.S. soil in the last year.

Nuclear attack, however, was not the only threat. Only last month TRANSLTR had thwarted one of the most ingeniously conceived terrorist attacks the NSA had ever witnessed. An anti‑government organization had devised a plan, code‑named Sherwood Forest. It targeted the New York Stock Exchange with the intention of “redistributing the wealth.” Over the course of six days, members of the group placed twenty‑seven nonexplosive flux pods in the buildings surrounding the Exchange. These devices, when detonated, create a powerful blast of magnetism. The simultaneous discharge of these carefully placed pods would create a magnetic field so powerful that all magnetic media in the Stock Exchange would be erased‑computer hard drives, massive ROM storage banks, tape backups, and even floppy disks. All records of who owned what would disintegrate permanently.

Because pinpoint timing was necessary for simultaneous detonation of the devices, the flux pods were interconnected over Internet telephone lines. During the two‑day countdown, the pods’ internal clocks exchanged endless streams of encrypted synchronization data. The NSA intercepted the data‑pulses as a network anomaly but ignored them as a seemingly harmless exchange of gibberish. But after TRANSLTR decrypted the data streams, analysts immediately recognized the sequence as a network‑synchronized countdown. The pods were located and removed a full three hours before they were scheduled to go off.

Susan knew that without TRANSLTR the NSA was helpless against advanced electronic terrorism. She eyed the Run‑Monitor. It still read over fifteen hours. Even if Tankado’s file broke right now, the NSA was sunk. Crypto would be relegated to breaking less than two codes a day. Even at the present rate of 150 a day, there was still a backlog of files awaiting decryption.

* * *

“Tankado called me last month,” Strathmore said, interrupting Susan’s thoughts.

Susan looked up. “Tankado called you?”

He nodded. “To warn me.”

“Warn you? He hates you.”

“He called to tell me he was perfecting an algorithm that wrote unbreakable codes. I didn’t believe him.”

“But why would he tell you about it?” Susan demanded. “Did he want you to buy it?”

“No. It was blackmail.”

Things suddenly began falling into place for Susan. “Of course,” she said, amazed. “He wanted you to clear his name.”

“No,” Strathmore frowned. “Tankado wanted TRANSLTR.”

“TRANSLTR?”

“Yes. He ordered me to go public and tell the world we have TRANSLTR. He said if we admitted we can read public E‑mail, he would destroy Digital Fortress.”

Susan looked doubtful.

Strathmore shrugged. “Either way, it’s too late now. He’s posted a complimentary copy of Digital Fortress at his Internet site. Everyone in the world can download it.”

Susan went white. “He what!”

“It’s a publicity stunt. Nothing to worry about. The copy he posted is encrypted. People can download it, but nobody can open it. It’s ingenious, really. The source code for Digital Fortress has been encrypted, locked shut.”

Susan looked amazed. “Of course! So everybody can have a copy, but nobody can open it.”

“Exactly. Tankado’s dangling a carrot.”

“Have you seen the algorithm?”

The commander looked puzzled. “No, I told you it’s encrypted.”

Susan looked equally puzzled. “But we’ve got TRANSLTR; why not just decrypt it?” But when Susan saw Strathmore’s face, she realized the rules had changed. “Oh my God.” She gasped, suddenly understanding. “Digital Fortress is encrypted with itself?”

Strathmore nodded. “Bingo.”

Susan was amazed. The formula for Digital Fortress had been encrypted using Digital Fortress. Tankado had posted a priceless mathematical recipe, but the text of the recipe had been scrambled. And it had used itself to do the scrambling.

“It’s Biggleman’s Safe,” Susan stammered in awe.

Strathmore nodded. Biggleman’s Safe was a hypothetical cryptography scenario in which a safe builder wrote blueprints for an unbreakable safe. He wanted to keep the blueprints a secret, so he built the safe and locked the blueprints inside. Tankado had done the same thing with Digital Fortress. He’d protected his blueprints by encrypting them with the formula outlined in his blueprints.

“And the file in TRANSLTR?” Susan asked.

“I downloaded it from Tankado’s Internet site like everyone else. The NSA is now the proud owner of the Digital Fortress algorithm; we just can’t open it.”

Susan marveled at Ensei Tankado’s ingenuity. Without revealing his algorithm, he had proven to the NSA that it was unbreakable.

Strathmore handed her a newspaper clipping. It was a translated blurb from the Nikkei Shimbun, the Japanese equivalent of the Wall Street Journal, stating that the Japanese programmer Ensei Tankado had completed a mathematical formula he claimed could write unbreakable codes. The formula was called Digital Fortress and was available for review on the Internet. The programmer would be auctioning it off to the highest bidder. The column went on to say that although there was enormous interest in Japan, the few U.S. software companies who had heard about Digital Fortress deemed the claim preposterous, akin to turning lead to gold. The formula, they said, was a hoax and not to be taken seriously.

Susan looked up. “An auction?”

Strathmore nodded. “Right now every software company in Japan has downloaded an encrypted copy of Digital Fortress and is trying to crack it open. Every second they can’t, the bidding price climbs.”

“That’s absurd,” Susan shot back. “All the new encrypted files are uncrackable unless you have TRANSLTR. Digital Fortress could be nothing more than a generic, public‑domain algorithm, and none of these companies could break it.”

“But it’s a brilliant marketing ploy,” Strathmore said. “Think about it‑all brands of bulletproof glass stop bullets, but if a company dares you to put a bullet through theirs, suddenly everybody’s trying.”

“And the Japanese actually believe Digital Fortress is different? Better than everything else on the market?”

“Tankado may have been shunned, but everybody knows he’s a genius. He’s practically a cult icon among hackers. If Tankado says the algorithm’s unbreakable, it’s unbreakable.”

But they’re all unbreakable as far as the public knows!”

“Yes . . .” Strathmore mused. “For the moment.”

“What’s that supposed to mean?”

Strathmore sighed. “Twenty years ago no one imagined we’d be breaking twelve‑bit stream ciphers. But technology progressed. It always does. Software manufacturers assume at some point computers like TRANSLTR will exist. Technology is progressing exponentially, and eventually current public‑key algorithms will lose their security. Better algorithms will be needed to stay ahead of tomorrow’s computers.”

“And Digital Fortress is it?”

“Exactly. An algorithm that resists brute force will never become obsolete, no matter how powerful code‑breaking computers get. It could become a world standard overnight.”

Susan pulled in a long breath. “God help us,” she whispered. “Can we make a bid?”

Date: 2015-12-24; view: 660