Digital Fortress

Chapter 33-36
Chapter 33

Tokugen Numataka stared out his window and paced like a caged animal. He had not yet heard from his contact, North Dakota. Damn Americans! No sense of punctuality!

He would have called North Dakota himself, but he didn't have a phone number for him. Numataka hated doing business this way-with someone else in control.

The thought had crossed Numataka's mind from the beginning that the calls from North Dakota could be a hoax-a Japanese competitor playing him for the fool. Now the old doubts were coming back. Numataka decided he needed more information.

He burst from his office and took a left down Numatech's main hallway. His employees bowed reverently as he stormed past. Numataka knew better than to believe they actually loved him-bowing was a courtesy Japanese employees offered even the most ruthless of bosses.

Numataka went directly to the company's main switchboard. All calls were handled by a single operator on a Corenco 2000, twelve-line switchboard terminal. The woman was busy but stood and bowed as Numataka entered.

"Sit down," he snapped.

She obeyed.

"I received a call at four forty-five on my personal line today. Can you tell me where it came from?" Numataka kicked himself for not having done this earlier.

The operator swallowed nervously. "We don't have caller identification on this machine, sir. But I can contact the phone company. I'm sure they can help."

Numataka had no doubt the phone company could help. In this digital age, privacy had become a thing of the past; there was a record of everything. Phone companies could tell you exactly who had called you and how long you'd spoken.

"Do it," he commanded. "Let me know what you find out."

Chapter 34

Susan sat alone in Node 3, waiting for her tracer. Hale had decided to step outside and get some air-a decision for which she was grateful. Oddly, however, the solitude in Node 3 provided little asylum. Susan found herself struggling with the new connection between Tankado and Hale.

"Who will guard the guards?" she said to herself. Quis custodiet ipsos custodes. The words kept circling in her head. Susan forced them from her mind.

Her thoughts turned to David, hoping he was all right. She still found it hard to believe he was in Spain. The sooner they found the pass-keys and ended this, the better.

Susan had lost track of how long she'd been sitting there waiting for her tracer. Two hours? Three? She gazed out at the deserted Crypto floor and wished her terminal would beep. There was only silence. The late-summer sun had set. Overhead, the automatic fluorescents had kicked on. Susan sensed time was running out.

She looked down at her tracer and frowned. "Come on," she grumbled. "You've had plenty of time." She palmed her mouse and clicked her way into her tracer's status window. "How long have you been running, anyway?"

Susan opened the tracer's status window-a digital clock much like the one on TRANSLTR; it displayed the hours and minutes her tracer had been running. Susan gazed at the monitor expecting to see a readout of hours and minutes. But she saw something else entirely. What she saw stopped the blood in her veins.

TRACER ABORTED

"Tracer aborted!" she choked aloud. "Why?"

In a sudden panic, Susan scrolled wildly through the data, searching the programming for any commands that might have told the tracer to abort. But her search went in vain. It appeared her tracer had stopped all by itself. Susan knew this could mean only one thing-her tracer had developed a bug.

Susan considered "bugs" the most maddening asset of computer programming. Because computers followed a scrupulously precise order of operations, the most minuscule programming errors often had crippling effects. Simple syntactical errors-such as a programmer mistakenly inserting a comma instead of a period-could bring entire systems to their knees. Susan had always thought the term "bug" had an amusing origin:

It came from the world's first computer-the Mark 1-a room-size maze of electromechanical circuits built in 1944 in a lab at Harvard University. The computer developed a glitch one day, and no one was able to locate the cause. After hours of searching, a lab assistant finally spotted the problem. It seemed a moth had landed on one of the computer's circuit boards and shorted it out. From that moment on, computer glitches were referred to as bugs.

"I don't have time for this," Susan cursed.

Finding a bug in a program was a process that could take days. Thousands of lines of programming needed to be searched to find a tiny error-it was like inspecting an encyclopedia for a single typo.

Susan knew she had only one choice-to send her tracer again. She also knew the tracer was almost guaranteed to hit the same bug and abort all over again. Debugging the tracer would take time, time she and the commander didn't have.

But as Susan stared at her tracer, wondering what error she'd made, she realized something didn't make sense. She had used this exact same tracer last month with no problems at all. Why would it develop a glitch all of a sudden?

As she puzzled, a comment Strathmore made earlier echoed in her mind. Susan, I tried to send the tracer myself, but the data it returned was nonsensical.

Susan heard the words again. The data it returned...

She cocked her head. Was it possible? The data it returned?

If Strathmore had received data back from the tracer, then it obviously was working. His data was nonsensical, Susan assumed, because he had entered the wrong search strings-but nonetheless, the tracer was working.

Susan immediately realized that there was one other possible explanation for why her tracer aborted. Internal programming flaws were not the only reasons programs glitched; sometimes there were external forces-power surges, dust particles on circuit boards, faulty cabling. Because the hardware in Node 3 was so well tuned, she hadn't even considered it.

Susan stood and strode quickly across Node 3 to a large bookshelf of technical manuals. She grabbed a spiral binder marked SYS-OP and thumbed through. She found what she was looking for, carried the manual back to her terminal, and typed a few commands. Then she waited while the computer raced through a list of commands executed in the past three hours. She hoped the search would turn up some sort of external interrupt-an abort command generated by a faulty power supply or defective chip.

Moments later Susan's terminal beeped. Her pulse quickened. She held her breath and studied the screen.

ERROR CODE 22

Susan felt a surge of hope. It was good news. The fact that the inquiry had found an error code meant her tracer was fine. The trace had apparently aborted due to an external anomaly that was unlikely to repeat itself.

Error code 22. Susan racked her memory trying to remember what code 22 stood for. Hardware failures were so rare in Node 3 that she couldn't remember the numerical codings.

Susan flipped through the SYS-OP manual, scanning the list of error codes.

19: CORRUPT HARD PARTITION

20: DC SPIKE

21: MEDIA FAILURE

When she reached number 22, she stopped and stared a long moment. Baffled, she double-checked her monitor.

ERROR CODE 22

Susan frowned and returned to the SYS-OP manual. What she saw made no sense. The explanation simply read:

22: MANUAL ABORT

Chapter 35

Becker stared in shock at Rocio. "You sold the ring?"

The woman nodded, her silky red hair falling around her shoulders.

Becker willed it not to be true. "Pero... but..."

She shrugged and said in Spanish, "A girl near the park."

Becker felt his legs go weak. This can't be!

Rocio smiled coyly and motioned to the German. "El queria que lo guardara. He wanted to keep it, but I told him no. I've got Gitana blood in me, Gypsy blood; we Gitanas, in addition to having red hair, are very superstitious. A ring offered by a dying man is not a good sign."

"Did you know the girl?" Becker interrogated.

Rocio arched her eyebrows. "Vaya. You really want this ring, don't you?"

Becker nodded sternly. "Who did you sell it to?"

The enormous German sat bewildered on the bed. His romantic evening was being ruined, and he apparently had no idea why. "Was passiert?" he asked nervously. "What's happening?"

Becker ignored him.

"I didn't actually sell it," Rocio said. "I tried to, but she was just a kid and had no money. I ended up giving it to her. Had I known about your generous offer, I would have saved it for you."

"Why did you leave the park?" Becker demanded. "Somebody had died. Why didn't you wait for the police? And give them the ring?"

"I solicit many things, Mr. Becker, but trouble is not one of them. Besides, that old man seemed to have things under control."

"The Canadian?"

"Yes, he called the ambulance. We decided to leave. I saw no reason to involve my date or myself with the police."

Becker nodded absently. He was still trying to accept this cruel twist of fate. She gave the damn thing away!

"I tried to help the dying man," Rocio explained. "But he didn't seem to want it. He started with the ring-kept pushing it in our faces. He had these three crippled fingers sticking up. He kept pushing his hand at us-like we were supposed to take the ring. I didn't want to, but my friend here finally did. Then the guy died."

"And you tried CPR?" Becker guessed.

"No. We didn't touch him. My friend got scared. He's big, but he's a wimp." She smiled seductively at Becker. "Don't worry-he can't speak a word of Spanish."

Becker frowned. He was wondering again about the bruises on Tankado's chest. "Did the paramedics give CPR?"

"I have no idea. As I told you, we left before they arrived."

"You mean after you stole the ring." Becker scowled.

Rocio glared at him. "We did not steal the ring. The man was dying. His intentions were clear. We gave him his last wish."

Becker softened. Rocio was right; he probably would have done the same damn thing. "But then you gave the ring to some girl?"

"I told you. The ring made me nervous. The girl had lots of jewelry on. I thought she might like it."

"And she didn't think it was strange? That you'd just give her a ring?"

"No. I told her I found it in the park. I thought she might offer to pay me for it, but she didn't. I didn't care. I just wanted to get rid of it."

"When did you give it to her?"

Rocio shrugged. "This afternoon. About an hour after I got it."

Becker checked his watch: 11:48 p.m. The trail was eight hours old. What the hell am I doing here? I'm supposed to be in the Smokys. He sighed and asked the only question he could think of. "What did the girl look like?"

"Era un punki," Rocio replied.

Becker looked up, puzzled. "Un punki?"

"Si. Punki."

"A punk?"

"Yes, a punk," she said in rough English, and then immediately switched back to Spanish. "Mucha joyeria. Lots of jewelry. A weird pendant in one ear. A skull, I think."

"There are punk rockers in Seville?"

Rocio smiled. "Todo bajo el sol. Everything under the sun." It was the motto of Seville's Tourism Bureau.

"Did she give you her name?"

"No."

"Did she say where she was going?"

"No. Her Spanish was poor."

"She wasn't Spanish?" Becker asked.

"No. She was English, I think. She had wild hair-red, white, and blue."

Becker winced at the bizarre image. "Maybe she was American," he offered.

"I don't think so," Rocio said. "She was wearing a T-shirt that looked like the British flag."

Becker nodded dumbly. "Okay. Red, white, and blue hair, a British flag T-shirt, a skull pendant in her ear. What else?"

"Nothing. Just your average punk."

Average punk? Becker was from a world of collegiate sweatshirts and conservative haircuts-he couldn't even picture what the woman was talking about. "Can you think of anything else at all?" he pressed.

Rocio thought a moment. "No. That's it."

Just then the bed creaked loudly. Rocio's client shifted his weight uncomfortably. Becker turned to him and spoke influent German. "Noch et was? Anything else? Anything to help me find the punk rocker with the ring?"

There was a long silence. It was as if the giant man had something he wanted to say, but he wasn't sure how to say it. His lower lip quivered momentarily, there was a pause, and then he spoke. The four words that came out were definitely English, but they were barely intelligible beneath his thick German accent. "Fock off und die."

Becker gaped in shock. "I beg your pardon?

"Fock off und die," the man repeated, patting his left palm against his fleshy right forearm-a crude approximation of the Italian gesture for "f*ck you."

Becker was too drained to be offended. F*ck off and die? What happened to Das Wimp? He turned back to Rocio and spoke in Spanish. "Sounds like I've overstayed my welcome."

"Don't worry about him." She laughed. "He's just a little frustrated. He'll get what's coming to him." She tossed her hair and winked.

"Is there anything else?" Becker asked. "Anything you can tell me that might help?"

Rocio shook her head. "That's all. But you'll never find her. Seville is a big city-it can be very deceptive."

"I'll do the best I can." It's a matter of national security...

"If you have no luck," Rocio said, eyeing the bulging envelope in Becker's pocket, "please stop back. My friend will be sleeping, no doubt. Knock quietly. I'll find us an extra room. You'll see a side of Spain you'll never forget." She pouted lusciously.

Becker forced a polite smile. "I should be going." He apologized to the German for interrupting his evening.

The giant smiled timidly. "Keine Ursache."

Becker headed out the door. No problem? Whatever happened to "F*ck off and die"?

Chapter 36

"Manual abort?" Susan stared at her screen, mystified.

She knew she hadn't typed any manual abort command-at least not intentionally. She wondered if maybe she'd hit the wrong sequence of keys by mistake.

"Impossible," she muttered. According to the headers, the abort command had been sent less than twenty minutes ago. Susan knew the only thing she'd typed in the last twenty minutes washer privacy code when she'd stepped out to talk to the commander. It was absurd to think the privacy code could have been misinterpreted as an abort command.

Knowing it was a waste of time, Susan pulled up her ScreenLock log and double-checked that her privacy code had been entered properly. Sure enough, it had.

"Then where," she demanded angrily, "where did it get a manual abort?"

Susan scowled and closed the ScreenLock window. Unexpectedly, however, in the split second as the window blipped away, something caught her eye. She reopened the window and studied the data. It made no sense. There was a proper "locking" entry when she'd left Node 3, but the timing of the subsequent "unlock" entry seemed strange. The two entries were less than one minute apart. Susan was certain she'd been outside with the commander for more than one minute.

Susan scrolled down the page. What she saw left her aghast. Registering three minutes later, a second set of lock-unlock entries appeared. According to the log, someone had unlocked her terminal while she was gone.

"Not possible!" she choked. The only candidate was Greg Hale, and Susan was quite certain she'd never given Hale her privacy code. Following good cryptographic procedure, Susan had chosen her code at random and never written it down; Hale's guessing the correct five-character alphanumeric was out of the question-it was thirty-six to the fifth power, over sixty million possibilities.

But the ScreenLock entries were as clear as day. Susan stared at them in wonder. Hale had somehow been on her terminal while she was gone. He had sent her tracer a manual abort command.

The questions of how quickly gave way to questions of why? Hale had no motive to break into her terminal. He didn't even know Susan was running a tracer. Even if he did know, Susan thought, why would he object to her tracking some guy named North Dakota?

The unanswered questions seemed to be multiplying in her head. "First things first," she said aloud. She would deal with Hale in a moment. Focusing on the matter at hand, Susan reloaded her tracer and hit the enter key. Her terminal beeped once.

TRACER SENT

Susan knew the tracer would take hours to return. She cursed Hale, wondering how in the world he'd gotten her privacy code, wondering what interest he had in her tracer.

Susan stood up and strode immediately for Hale's terminal. The screen was black, but she could tell it was not locked-the monitor was glowing faintly around the edges. Cryptographers seldom locked their terminals except when they left Node 3 for the night. Instead, they simply dimmed the brightness on their monitors-a universal, honor-code indication that no one should disturb the terminal.

Susan reached for Hale's terminal. "Screw the honor code," she said. "What the hell are you up to?"

Throwing a quick glance out at the deserted Crypto floor, Susan turned up Hale's brightness controls. The monitor came into focus, but the screen was entirely empty. Susan frowned at the blank screen. Uncertain how to proceed, she called up a search engine and typed:

SEARCH FOR: "TRACER"

It was a long shot, but if there were any references to Susan's tracer in Hale's computer, this search would find them. It might shed some light on why Hale had manually aborted her program. Seconds later the screen refreshed.

NO MATCHES FOUND

Susan sat a moment, unsure what she was even looking for. She tried again.

SEARCH FOR: "SCREENLOCK"

The monitor refreshed and provided a handful of innocuous references-no hint that Hale had any copies of Susan's privacy code on his computer.

Susan sighed loudly. So what programs has he been using today? She went to Hale's "recent applications" menu to find the last program he had used. It was his E-mail server. Susan searched his hard drive and eventually found his E-mail folder hidden discreetly inside some other directories. She opened the folder, and additional folders appeared; it seemed Hale had numerous E-mail identities and accounts. One of them, Susan noticed with little surprise, was an anonymous account. She opened the folder, clicked one of the old, inbound messages, and read it.

She instantly stopped breathing. The message read:

TO: [email protected]

FROM: [email protected]

GREAT PROGRESS! DIGITAL FORTRESS IS ALMOST DONE.

THIS THING WILL SET THE NSA BACK DECADES!

As if in a dream, Susan read the message over and over. Then, trembling, she opened another.

TO: [email protected]

FROM: [email protected]

ROTATING CLEARTEXT WORKS! MUTATION STRINGS ARE THE TRICK!

It was unthinkable, and yet there it was. E-mail from Ensei Tankado. He had been writing to Greg Hale. They were working together. Susan went numb as the impossible truth stared up at her from the terminal.

Greg Hale is NDAKOTA?

Susan's eyes locked on the screen. Her mind searched desperately for some other explanation, but there was none. It was proof-sudden and inescapable: Tankado had used mutation strings to create a rotating cleartext function, and Hale had conspired with him to bring down the NSA.

"It's..." Susan stammered. "It's... not possible."

As if to disagree, Hale's voice echoed from the past: Tankado wrote me a few times... Strathmore took a gamble hiring me... I'm getting out of here someday.

Still, Susan could not accept what she was seeing. True, Greg Hale was obnoxious and arrogant-but he wasn't a traitor. He knew what Digital Fortress would do to the NSA; there was no way he was involved in a plot to release it!

And yet, Susan realized, there was nothing to stop him-nothing except honor and decency. She thought of the Skipjack algorithm. Greg Hale had ruined the NSA's plans once before. What would prevent him from trying again?

"But Tankado..." Susan puzzled. Why would someone as paranoid as Tankado trust someone as unreliable as Hale?

She knew that none of it mattered now. All that mattered was getting to Strathmore. By some ironic stroke of fate, Tankado's partner was right there under their noses. She wondered if Hale knew yet that Ensei Tankado was dead.

She quickly began closing Hale's E-mail files in order to leave the terminal exactly as she had found it. Hale could suspect nothing-not yet. The Digital Fortress pass-key, she realized in amazement, was probably hidden somewhere inside that very computer.

But as Susan closed the last of the files, a shadow passed outside the Node 3 window. Her gaze shot up, and she saw Greg Hale approaching. Her adrenaline surged. He was almost to the doors.

"Damn!" she cursed, eyeing the distance back to her seat. She knew she'd never make it. Hale was almost there.

She wheeled desperately, searching Node 3 for options. The doors behind her clicked. Then they engaged. Susan felt instinct takeover. Digging her shoes into the carpet, she accelerated in long, reaching strides toward the pantry. As the doors hissed open, Susan slid to a stop in front of the refrigerator and yanked open the door. A glass pitcher on top tipped precariously and then rocked to a stop.

"Hungry?" Hale asked, entering Node 3 and walking toward her. His voice was calm and flirtatious. "Want to share some tofu?"

Susan exhaled and turned to face him. "No thanks," she offered. "I think I'll just-" But the words got caught in her throat. She went white.

Hale eyed her oddly. "What's wrong?"

Susan bit her lip and locked eyes with him. "Nothing, "she managed. But it was a lie. Across the room, Hale's terminal glowed brightly. She'd forgotten to dim it.