Back Point of Contact Save as PDF
Chapters (83)
  1. Cover
  2. ALSO BY TOM CLANCY
  3. PRINCIPAL CHARACTERS
  4. 1
  5. 2
  6. 3
  7. 4
  8. 5
  9. 6
  10. 7
  11. 8
  12. 9
  13. 10
  14. 11
  15. 12
  16. 13
  17. 14
  18. 15
  19. 16
  20. 17
  21. 18
  22. 19
  23. 20
  24. 21
  25. 22
  26. 23
  27. 24
  28. 25
  29. 26
  30. 27
  31. 28
  32. 29
  33. 30
  34. 31
  35. 32
  36. 33
  37. 34
  38. 35
  39. 36
  40. 37
  41. 38
  42. 39
  43. 40
  44. 41
  45. 42
  46. 43
  47. 44
  48. 45
  49. 46
  50. 47
  51. 48
  52. 49
  53. 50
  54. 51
  55. 52
  56. 53
  57. 54
  58. 55
  59. 56
  60. 57
  61. 58
  62. 59
  63. 60
  64. 61
  65. 62
  66. 63
  67. 64
  68. 65
  69. 66
  70. 67
  71. 68
  72. 69
  73. 70
  74. 71
  75. 72
  76. 73
  77. 74
  78. 75
  79. 76
  80. 77
  81. 78
  82. 79
  83. What’s next onyour reading list?

After thinking about the Dalfan security protocols all day, Paul finally figured out a way to work around them. Like most brilliant solutions to complex problems, it was frighteningly simple. It was also kind of crazy.

His plan had only a few moving parts: Download the CIA program onto his laptop, then copy the CIA program from his laptop to a Dalfan encrypted USB. Once it was infected, Paul would then install the Dalfan USB into a Dalfan desktop and, thirty seconds later, his mission would be completed.

Tonight was the easy piece. All he had to do was download the CIA program from Rhodes’s USB drive to his laptop. Easy.

Unless it didn’t work.

Relax, he told himself. One step at a time.

He double-checked the lock on his bedroom door to make sure Jack wouldn’t suddenly walk in. No point in getting him tangled up in this mess.

He then sat on his bed and opened his laptop in order to load Rhodes’s CIA drive onto his computer. But what did Rhodes say? It was an automatically executing file. But it would execute only after he used his thumbprint to unlock it and typed in his verification code. Once he did those two things, the program would automatically launch.

That was a problem. Paul didn’t want the program to launch automatically—otherwise, he might not be able to copy it.

But Paul figured out a crack in the system. He inserted the CIA drive into the USB port, then pressed his thumb against the thumb pad. The drive recognized Paul’s print. It unlocked, as expected, flashing red, then blue.

The laptop screen then flashed a dialogue box, asking Paul for his security code, which would initiate the program launch. Paul ignored it. Instead, he opened up the USB drive icon on his laptop and examined its contents.

Paul saw a single unnamed file folder. The file didn’t appear to be doing anything. So far, so good.

He swallowed hard, then dragged the unnamed CIA file onto his laptop. A copy progress bar opened up. It was going to take about two minutes to transfer. Paul drummed his fingers nervously, waiting for the transfer to complete . . .

. . . waiting for an explosion.

It never came.

The progress bar completed, and the CIA file was successfully copied to his machine’s desktop. He ejected the CIA drive and the passcode dialogue box disappeared.

Paul stared at the copied file on his screen. It didn’t seem to be doing anything.

What was really interesting to Paul was that his MilSpec-grade antivirus software wasn’t picking up anything. In theory, the CIA program hadn’t launched inside his computer because he hadn’t entered his passcode.

Paul’s heart raced as panic set in. How could he enter his passcode and launch it on the Dalfan machine without the CIA drive inserted? Maybe the CIA program wouldn’t run on the Dalfan· machine without it.