Digital Fortess - Brown Dan - Страница 10

• Предыдущая
• 10/80
• Следующая

Strathmore shook his head. “Tankado gave us our chance. He made that clear. It’s too risky anyway; if we get caught, we’re basically admitting that we’re afraid of his algorithm. We’d be making a public confession not only that we have TRANSLTR but that Digital Fortress is immune.”

“What’s the time frame?”

Strathmore frowned. “Tankado planned to announce the highest bidder tomorrow at noon.”

Susan felt her stomach tighten. “Then what?”

“The arrangement was that he would give the winner the pass?key.”

“The pass?key?”

“Part of the ploy. Everybody’s already got the algorithm, so Tankado’s auctioning off the pass?key that unlocks it.”

Susan groaned. “Of course.” It was perfect. Clean and simple. Tankado had encrypted Digital Fortress, and he alone held the pass?key that unlocked it. She found it hard to fathom that somewhere out there?probably scrawled on a piece of paper in Tankado’s pocket?there was a sixty?four?character pass?key that could end U.S. intelligence gathering forever.

Susan suddenly felt ill as she imagined the scenario. Tankado would give his pass?key to the highest bidder, and that company would unlock the Digital Fortress file. Then it probably would embed the algorithm in a tamper?proof chip, and within five years every computer would come preloaded with a Digital Fortress chip. No commercial manufacturer had ever dreamed of creating an encryption chip because normal encryption algorithms eventually become obsolete. But Digital Fortress would never become obsolete; with a rotating cleartext function, no brute?force attack would ever find the right key. A new digital encryption standard. From now until forever. Every code unbreakable. Bankers, brokers, terrorists, spies. One world?one algorithm.

Anarchy.

“What are the options?” Susan probed. She was well aware that desperate times called for desperate measures, even at the NSA.

“We can’t remove him, if that’s what you’re asking.”

It was exactly what Susan was asking. In her years with the NSA, Susan had heard rumors of its loose affiliations with the most skilled assassins in the world?hired hands brought in to do the intelligence community’s dirty work.

Strathmore shook his head. “Tankado’s too smart to leave us an option like that.”

Susan felt oddly relieved. “He’s protected?”

“Not exactly.”

“In hiding?”

Strathmore shrugged. “Tankado left Japan. He planned to check his bids by phone. But we know where he is.”

“And you don’t plan to make a move?”

“No. He’s got insurance. Tankado gave a copy of his pass?key to an anonymous third party . . . in case anything happened.”

Of course, Susan marveled. A guardian angel. “And I suppose if anything happens to Tankado, the mystery man sells the key?”

“Worse. Anyone hits Tankado, and his partner publishes.”

Susan looked confused. “His partner publishes the key?”

Strathmore nodded. “Posts it on the Internet, puts it in newspapers, on billboards. In effect, he gives it away.”

Susan’s eyes widened. “Free downloads?”

“Exactly. Tankado figured if he was dead, he wouldn’t need the money?why not give the world a little farewell gift?”

There was a long silence. Susan breathed deeply as if to absorb the terrifying truth. Ensei Tankado has created an unbreakable algorithm. He’s holding us hostage.

She suddenly stood. Her voice was determined. “We must contact Tankado! There must be a way to convince him not to release! We can offer him triple the highest bid! We can clear his name! Anything!”

“Too late,” Strathmore said. He took a deep breath. “Ensei Tankado was found dead this morning in Seville, Spain.”

The twin?engine Learjet 60 touched down on the scorching runway. Outside the window, the barren landscape of Spain’s lower extremadura blurred and then slowed to a crawl.

“Mr. Becker?” a voice crackled. “We’re here.”

Becker stood and stretched. After unlatching the overhead compartment, he remembered he had no luggage. There had been no time to pack. It didn’t matter?he’d been promised the trip would be brief, in and out.

As the engines wound down, the plane eased out of the sun and into a deserted hangar opposite the main terminal. A moment later the pilot appeared and popped the hatch. Becker tossed back the last of his cranberry juice, put the glass on the wet bar, and scooped up his suit coat.

The pilot pulled a thick manila envelope from his flight suit. “I was instructed to give you this.” He handed it to Becker. On the front, scrawled in blue pen, were the words:

KEEP THE CHANGE.

Becker thumbed through the thick stack of reddish bills. “What the . . . ?”

“Local currency,” the pilot offered flatly.

“I know what it is,” Becker stammered. “But it’s . . . it’s too much. All I need is taxi fare.” Becker did the conversion in his head. “What’s in here is worth thousands of dollars!”

“I have my orders, sir.” The pilot turned and hoisted himself back into the cabin. The door slid shut behind him.

Becker stared up at the plane and then down at the money in his hand. After standing a moment in the empty hangar, he put the envelope in his breast pocket, shouldered his suit coat, and headed out across the runway. It was a strange beginning. Becker pushed it from his mind. With a little luck he’d be back in time to salvage some of his Stone Manor trip with Susan.

In and out, he told himself. In and out.

There was no way he could have known.

Systems security technician Phil Chartrukian had only intended to be inside Crypto a minute?just long enough to grab some paperwork he’d forgotten the day before. But it was not to be.

After making his way across the Crypto floor and stepping into the Sys?Sec lab, he immediately knew something was not right. The computer terminal that perpetually monitored TRANSLTR’s internal workings was unmanned and the monitor was switched off.

Chartrukian called out, “Hello?”

There was no reply. The lab was spotless?as if no one had been there for hours.

Although Chartrukian was only twenty?three and relatively new to the Sys?Sec squad, he’d been trained well, and he knew the drill: There was always a Sys?Sec on duty in Crypto . . . especially on Saturdays when no cryptographers were around.

He immediately powered up the monitor and turned to the duty board on the wall. “Who’s on watch?” he demanded aloud, scanning the list of names. According to the schedule, a young rookie named Seidenberg was supposed to have started a double shift at midnight the night before. Chartrukian glanced around the empty lab and frowned. “So where the hell is he?”

As he watched the monitor power up, Chartrukian wondered if Strathmore knew the Sys?Sec lab was unmanned. He had noticed on his way in that the curtains of Strathmore’s workstation were closed, which meant the boss was in?not at all uncommon for a Saturday; Strathmore, despite requesting his cryptographers take Saturdays off, seemed to work 365 days a year.

There was one thing Chartrukian knew for certain?if Strathmore found out the Sys?Sec lab was unmanned, it would cost the absent rookie his job. Chartrukian eyed the phone, wondering if he should call the young techie and bail him out; there was an unspoken rule among Sys?Sec that they would watch each other’s backs. In Crypto, Sys?Secs were second?class citizens, constantly at odds with the lords of the manor. It was no secret that the cryptographers ruled this multibillion?dollar roost; Sys?Secs were tolerated only because they kept the toys running smoothly.

Chartrukian made his decision. He grabbed the phone. But the receiver never reached his ear. He stopped short, his eyes transfixed on the monitor now coming into focus before him. As if in slow motion, he set down the phone and stared in open?mouthed wonder.

• Предыдущая
• 10/80
• Следующая