- •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
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.