Back Fall; or, Dodge in Hell
Chapters (77)
  1. Title Page
  2. Contents
  3. Dedication
  4. Book 1
  5. Part 1
  6. Chapter 1
  7. Chapter 2
  8. Chapter 3
  9. Chapter 4
  10. Chapter 5
  11. Chapter 6
  12. Chapter 7
  13. Chapter 8
  14. Part 2
  15. Chapter 9
  16. Chapter 10
  17. Chapter 11
  18. Part 3
  19. Chapter 12
  20. Chapter 13
  21. Chapter 14
  22. Chapter 15
  23. Chapter 16
  24. Part 4
  25. Chapter 17
  26. Chapter 18
  27. Chapter 19
  28. Chapter 20
  29. Chapter 21
  30. Chapter 22
  31. Chapter 23
  32. Chapter 24
  33. Part 5
  34. Chapter 25
  35. Chapter 26
  36. Chapter 27
  37. Chapter 28
  38. Chapter 29
  39. Chapter 30
  40. Chapter 31
  41. Chapter 32
  42. Part 6
  43. Chapter 33
  44. Chapter 34
  45. Chapter 35
  46. Chapter 36
  47. Chapter 37
  48. Chapter 38
  49. Chapter 39
  50. Chapter 40
  51. Chapter 41
  52. Part 7
  53. Chapter 42
  54. Book 2
  55. Part 8
  56. Chapter 43
  57. Chapter 44
  58. Part 9
  59. Chapter 45
  60. Chapter 46
  61. Chapter 47
  62. Part 10
  63. Chapter 48
  64. Chapter 49
  65. Part 11
  66. Chapter 50
  67. Chapter 51
  68. Chapter 52
  69. Chapter 53
  70. Chapter 54
  71. Chapter 55
  72. Chapter 56
  73. Map of The Land
  74. Acknowledgments
  75. About The Author
  76. Also By Neal Stephenson
  77. Copyright

It was only after the plates had been cleared away and coffee served that C-plus had buckled down to the serious business of making her a token holder—or, in the inevitable tech industry abbreviation, a toho—with access privileges to Dodge’s Brain.

In essence, this was no different from handing someone a key to an apartment or giving them the combination to a padlock. There was this entity in the cloud called Dodge’s Brain. It was mostly just a passive, inert repository of data. But it did include some executables—some actual running code—that were active all the time, like a sentry pacing back and forth in front of a locked library door. That code was as secure and unhackable as it was possible for anything to be in this world, and it would only open the door for entities that could prove—and keep proving—that they had been granted the requisite authority.

Corvallis Kawasaki had the power to confer those tokens on others. In the Meatspace world, “others” meant “human beings.” But the digital sentry in front of the door was just a computer program running on a server somewhere, or more likely distributed across a number of servers. It didn’t really have the ability to recognize humans, or to reliably tell one human from another.

“We could use biometrics,” C-plus admitted. Meaning, devices like fingerprint readers or iris scanners. “But that just moves the vulnerability elsewhere. Let’s say I had a gadget that could read your fingerprint with one hundred percent accuracy. Fine. The gadget knows it’s Sophia. But in order for that to be of any use, the gadget has to send a message to some other process, somewhere in the world, saying, ‘I checked her fingerprint and it’s definitely Sophia.’”

“And that could be hacked.”

“Yeah. Still, probably good enough. But I am trying to abide by the highest possible standards here.”

“To make a point. To set an example,” Sophia said.

“And to avoid looking like a fool,” he said. “If it came out that I had let standards slip, cut corners, and gotten burned, it would be embarrassing.”

“Fair enough.”

“Now, passwords are ridiculously old-school, but they work as a stopgap. I want you to make one up, right now. One that you’ve never used before and will never use for any other purpose. Take your time. When you’re ready, type it in.” Uncle C slid a tablet across the table to her, keyboard ready for text entry.

“Okay. Thinking,” Sophia said.

“Because this is your password to DB, you’re probably thinking about using a password or phrase that has some kind of sentimental connection to your uncle Richard. Some kind of personal meaning to you. Don’t. This isn’t magic. It’s not an opportunity for you to express your feelings.”