- •Dan Brown Digital Fortress
- •Prologue
- •Chapter 1
- •Chapter 2
- •Chapter 3
- •National security agency (nsa) crypto facility authorized personnel only
- •Hl fkzc vd lds
- •Im glad we met
- •Chapter 4
- •Chapter 5
- •Employee carl austin terminated for inappropriate conduct.
- •Time elapsed: 15:09:33 awaiting key: ________
- •Chapter 6
- •Chapter 7
- •“Transltr?”
- •Chapter 8
- •Keep the change.
- •Chapter 9
- •Time elapsed: 15:17:21
- •Chapter 10
- •Chapter 11
- •Chapter 12
- •Chapter 13
- •Chapter 14
- •Chapter 15
- •Chapter 16
- •Chapter 17
- •Chapter 18
- •Chapter 19
- •Chapter 20
- •Chapter 21
- •Chapter 22
- •Chapter 23
- •Chapter 24
- •Chapter 25
- •Subject: p. Cloucharde‑terminated
- •Message sent chapter 26
- •Chapter 27
- •Dinner at alfredo’s? 8 pm?
- •Chapter 28
- •Chapter 29
- •Please accept this humble fax my love for you is without wax.
- •Tracer searching . . .
- •Tracer abort?
- •Chapter 30
- •Chapter 31
- •Chapter 32
- •Chapter 33
- •Chapter 34
- •Tracer aborted
- •Error code 22
- •Chapter 36
- •Tracer sent
- •Search for: “tracer”
- •No matches found
- •Search for: “screenlock”
- •Great progress! digital fortress is almost done. This thing will set the nsa back decades!
- •Rotating cleartext works! mutation strings are the trick!
- •Chapter 37
- •Chapter 38
- •Chapter 39
- •Chapter 40
- •Chapter 41
- •Subject: rocio eva granada‑terminated subject: hans huber‑terminated
- •Chapter 42
- •Chapter 43
- •Crypto‑production/expenditure
- •Chapter 44
- •Chapter 45
- •Chapter 46
- •Chapter 47
- •Chapter 48
- •Chapter 49
- •Chapter 50
- •Crypto sublevels authorized personnel only
- •Chapter 51
- •Chapter 52
- •Chapter 53
- •Chapter 54
- •Chapter 55
- •Chapter 56
- •Chapter 57
- •Chapter 58
- •Chapter 59
- •Chapter 60
- •Chapter 61
- •Chapter 62
- •Chapter 63
- •Chapter 64
- •Chapter 65
- •Chapter 66
- •Chapter 67
- •Chapter 68
- •Chapter 69
- •Chapter 70
- •Chapter 71
- •Chapter 72
- •Abort run
- •Chapter 73
- •Chapter 74
- •Chapter 75
- •Chapter 76
- •Chapter 77
- •Chapter 78
- •Chapter 79
- •Chapter 80
- •Chapter 81
- •Chapter 82
- •Chapter 83
- •Chapter 84
- •Chapter 85
- •Chapter 86
- •Sorry. Unable to abort. Sorry. Unable to abort. Sorry. Unable to abort.
- •Tell the world about transltr only the truth will save you now . . .
- •Only the truth will save you now
- •Enter pass‑key
- •Chapter 87
- •Chapter 88
- •Chapter 89
- •Chapter 90
- •Chapter 91
- •Chapter 92
- •Chapter 93
- •Chapter 94
- •Chapter 95
- •Chapter 96
- •Chapter 97
- •Chapter 98
- •Chapter 99
- •Chapter 100
- •Subject: david becker‑terminated
- •Chapter 101
- •Chapter 102
- •Chapter 103
- •Chapter 105
- •Chapter 106
- •Chapter 107
- •Chapter 108
- •Chapter 109
- •Only the truth will save you now enter pass‑key ______
- •Only the truth will save you now enter pass‑key ______
- •Chapter 110
- •Chapter 111
- •Chapter 112
- •Chapter 113
- •Chapter 114
- •Chapter 115
- •Chapter 116
- •Chapter 117
- •Only the truth will save you now
- •Chapter 118
- •Quiscustodietipsoscustodes
- •Chapter 119
- •Illegal entry. Numeric field only.
- •Chapter 120
- •Pfee sesn retm
- •Pfee sesn retm mfha irwe ooig meen nrma enet shas dcns iiaa ieer brnk fble lodi
- •Pfeesesnretmpfhairweooigmeennrmaenetshasdcnsiiaaieerbrnkfblelodi
- •Chapter 121
- •Chapter 122
- •Primedifferencebetweenelementsresponsibleforhiroshimaandnagasaki
- •Chapter 123
- •Prime difference between elements responsible for hiroshima and nagasaki
- •Chapter 124
- •Prime difference between elements responsible forhiroshima and nagasaki
- •Chapter 125
- •Chapter 126
- •Chapter 127
- •Enter pass‑key? 3
- •Kill code confirmed.
- •Chapter 128
- •Epilogue
Chapter 18
Standing before the huge plate‑glass window in his Tokyo skyrise, Numataka took a long pull on his cigar and smiled to himself. He could scarcely believe his good fortune. He had spoken to the American again, and if all was going according to the timetable, Ensei Tankado had been eliminated by now, and his copy of the pass‑key had been confiscated.
It was ironic, Numataka thought, that he himself would end up with Ensei Tankado’s pass‑key. Tokugen Numataka had met Tankado once many years ago. The young programmer had come to Numatech Corp. fresh out of college, searching for a job. Numataka had denied him. There was no question that Tankado was brilliant, but at the time there were other considerations. Although Japan was changing, Numataka had been trained in the old school; he lived by the code of menboko‑honor and face. Imperfection was not to be tolerated. If he hired a cripple, he would bring shame on his company. He had disposed of Tankado’s resume without a glance.
Numataka checked his watch again. The American, North Dakota, should have called by now. Numataka felt a tinge of nervousness. He hoped nothing was wrong.
If the pass‑keys were as good as promised, they would unlock the most sought‑after product of the computer age‑a totally invulnerable digital encryption algorithm. Numataka could embed the algorithm in tamper‑proof, spray‑sealed VSLI chips and mass market them to world computer manufacturers, governments, industries, and perhaps, even the darker markets . . . the black market of world terrorists.
Numataka smiled. It appeared, as usual, that he had found favor with the shichigosan‑the seven deities of good luck. Numatech Corp. was about to control the only copy of Digital Fortress that would ever exist. Twenty million dollars was a lot of money‑but considering the product, it was the steal of the century.
Chapter 19
“What if someone else is looking for the ring?” Susan asked, suddenly nervous. “Could David be in danger?”
Strathmore shook his head. “Nobody else knows the ring exists. That’s why I sent David. I wanted to keep it that way. Curious spooks don’t usually tail Spanish teachers.”
“He’s a professor,” Susan corrected, immediately regretting the clarification. Every now and again Susan got the feeling David wasn’t good enough for the commander, that he thought somehow she could do better than a schoolteacher.
“Commander,” she said, moving on, “if you briefed David by car phone this morning, someone could have intercepted the—”
“One‑in‑a‑million shot,” Strathmore interrupted, his tone reassuring. “Any eavesdropper had to be in the immediate vicinity and know exactly what to listen for.” He put his hand on her shoulder. “I would never have sent David if I thought it was dangerous.” He smiled. “Trust me. Any sign of trouble, and I’ll send in the pros.”
Strathmore’s words were punctuated by the sudden sound of someone pounding on the Node 3 glass. Susan and Strathmore turned.
Sys‑Sec Phil Chartrukian had his face pressed against the pane and was pounding fiercely, straining to see through. Whatever he was excitedly mouthing was not audible through the soundproofed glass. He looked like he’d seen a ghost.
“What the hell is Chartrukian doing here?” Strathmore growled. “He’s not on duty today.”
“Looks like trouble,” Susan said. “He probably saw the Run‑Monitor.”
“Goddamn it!” the commander hissed. “I specifically called the scheduled Sys‑Sec last night and told him not to come in!”
Susan was not surprised. Canceling a Sys‑Sec duty was irregular, but Strathmore undoubtedly had wanted privacy in the dome. The last thing he needed was some paranoid Sys‑Sec blowing the lid off Digital Fortress.
“We better abort TRANSLTR,” Susan said. “We can reset the Run‑Monitor and tell Phil he was seeing things.”
Strathmore appeared to consider it, then shook his head. “Not yet. TRANSLTR is fifteen hours into this attack. I want to run it a full twenty‑four‑just to be sure.”
This made sense to Susan. Digital Fortress was the first ever use of a rotating cleartext function. Maybe Tankado had overlooked something; maybe TRANSLTR would break it after twenty‑four hours. Somehow Susan doubted it.
“TRANSLTR keeps running,” Strathmore resolved. “I need to know for sure this algorithm is untouchable.”
Chartrukian continued pounding on the pane.
“Here goes nothing.” Strathmore groaned. “Back me up.”
The commander took a deep breath and then strode to the sliding glass doors. The pressure plate on the floor activated, and the doors hissed open.
Chartrukian practically fell into the room. “Commander, sir. I . . . I’m sorry to bother you, but the Run‑Monitor . . . I ran a virus probe and—”
“Phil, Phil, Phil,” the commander gushed pleasantly as he put a reassuring hand on Chartrukian’s shoulder. “Slow down. What seems to be the problem?”
From the easygoing tone in Strathmore’s voice, nobody would ever have guessed his world was falling in around him. He stepped aside and ushered Chartrukian into the sacred walls of Node 3. The Sys‑Sec stepped over the threshold hesitantly, like a well‑trained dog that knew better.
From the puzzled look on Chartrukian’s face, it was obvious he’d never seen the inside of this place. Whatever had been the source of his panic was momentarily forgotten. He surveyed the plush interior, the line of private terminals, the couches, the bookshelves, the soft lighting. When his gaze fell on the reigning queen of Crypto, Susan Fletcher, he quickly looked away. Susan intimidated the hell out of him. Her mind worked on a different plane. She was unsettlingly beautiful, and his words always seemed to get jumbled around her. Susan’s unassuming air made it even worse.
“What seems to be the problem, Phil?” Strathmore said, opening the refrigerator. “Drink?”
“No, ah‑no, thank you, sir.” He seemed tongue‑tied, not sure he was truly welcome. “Sir . . . I think there’s a problem with TRANSLTR.”
Strathmore closed the refrigerator and looked at Chartrukian casually. “You mean the Run‑Monitor?”
Chartrukian looked shocked. “You mean you’ve seen it?”
“Sure. It’s running at about sixteen hours, if I’m not mistaken.”
Chartrukian seemed puzzled. “Yes, sir, sixteen hours. But that’s not all, sir. I ran a virus probe, and it’s turning up some pretty strange stuff.”
“Really?” Strathmore seemed unconcerned. “What kind of stuff?”
Susan watched, impressed with the commander’s performance.
Chartrukian stumbled on. “TRANSLTR’s processing something very advanced. The filters have never seen anything like it. I’m afraid TRANSLTR may have some sort of virus.”
“A virus?” Strathmore chuckled with just a hint of condescension. “Phil, I appreciate your concern, I really do. But Ms. Fletcher and I are running a new diagnostic, some very advanced stuff. I would have alerted you to it, but I wasn’t aware you were on duty today.”
The Sys‑Sec did his best to cover gracefully. “I switched with the new guy. I took his weekend shift.”
Strathmore’s eyes narrowed. “That’s odd. I spoke to him last night. I told him not to come in. He said nothing about switching shifts.”
Chartrukian felt a knot rise in his throat. There was a tense silence.
“Well.” Strathmore finally sighed. “Sounds like an unfortunate mix‑up.” He put a hand on the Sys‑Sec’s shoulder and led him toward the door. “The good news is you don’t have to stay. Ms. Fletcher and I will be here all day. We’ll hold the fort. You just enjoy your weekend.”
Chartrukian was hesitant. “Commander, I really think we should check the—”
“Phil,” Strathmore repeated a little more sternly, “TRANSLTR is fine. If your probe saw something strange, it’s because we put it there. Now if you don’t mind . . .” Strathmore trailed off, and the Sys‑Sec understood. His time was up.
* * *
“A diagnostic, my ass!” Chartrukian muttered as he fumed back into the Sys‑Sec lab. “What kind of looping function keeps three million processors busy for sixteen hours?”
Chartrukian wondered if he should call the Sys‑Sec supervisor. Goddamn cryptographers, he thought. They just don’t understand security!
The oath Chartrukian had taken when he joined Sys‑Sec began running through his head. He had sworn to use his expertise, training, and instinct to protect the NSA’s multibillion‑dollar investment.
“Instinct,” he said defiantly. It doesn’t take a psychic to know this isn’t any goddamn diagnostic!
Defiantly, Chartrukian strode over to the terminal and fired up TRANSLTR’s complete array of system assessment software.
“Your baby’s in trouble, Commander,” he grumbled. “You don’t trust instinct? I’ll get you proof!”