"Now what?" LuEllen asked.
"We got their shooters. They might have more, but they'll be cautious. And now Maggie knows that we know, so there'll be no more bullshit."
"Is that good?"
"Maybe. I've got a couple of ideas. I've got to get on the terminal and talk to Bobby. You ought to get out of here. Back to Duluth. It'll all be computer stuff from here on. If we travel together, we'd just be easier to spot."
"You think they could spot us? They're not the cops, they're just a bunch of hoods."
"Yeah. But like Maggie said, why take a chance?"
"You're right," she said after a while. "But I'm not going back to Duluth."
"Where?"
"Mexico. Right where we were going. I'm all packed." And she started to cry.
We drove north through Cumberland across into Pennsylvania and arrived outside of Pittsburgh in the early morning hours, running, in the end, on pure adrenaline. We slept late, and in the evening I put her on a plane to San Diego.
"Take care of yourself, Kidd." LuEllen kissed me on the cheek and went through the gate. Unlike Maggie, she never looked back.
What?
Need long talk.
Call 3 a.m.
CHAPTER 19
Early the next morning I laid out a program for Bobby.
Big bux.
Yes.
Need 2 more hacks.
OK.
10K each for hacks.
OK.
25K for me. Cash. Pay when we win.
I pay out front. If we lose, I might not be able to pay. Give PO Box.
Leave terminal on answer.
I woke at midmorning to the terminal alarm and a squirt of data-a post office box in Memphis where I could send the money and registered mail, and also the names of the other two hacks. They were both from California. Bobby called them Cal Tech and Stanford. I couldn't remember either one, but Bobby said that Stanford met me on a Vegas gaming board a few years before. Bobby said he would begin checking Anshiser phone lines for incoming data.
Anshiser company/house show no incoming data lines. Must have private exchanges. Major pain.
Yes.
Most computers are hooked into the local telephone exchange. In simpler days, the data-line numbers were often variants of the telephone number of the company that owned the computers. If the company's number was 555-1115, the computer number might be 555-1116.
Hackers got onto that right away. Whole nights were spent exploring the guts of various expensive on-line computers. A generation of computer fanatics learned their jobs by doing it. The first illegal entry I made, way back in the early seventies, was to a call-in board that regulated the heating, cooling, water, and other systems of one of the biggest office buildings in Minneapolis. I could have turned off the building's heat in the middle of a January night, but I didn't. I left a note for the operator, though, and the next time I called, entry was more difficult.
A little later, computer security got tight enough that data-line numbers were moved well away from the company's regular phone-but still in the same exchange. Hackers fought back by producing autodial programs that would dial all of the ten thousand numbers in a given exchange. Whenever the modem got a carrier tone, the computer would note it. If there was no answer or a voice answer, the computer would hang up and move on. A computer could call a thousand numbers overnight, and it was a sad night that didn't produce a dozen new computer lines.
Eventually, security-phone companies began creating their own exchanges. The secret exchanges were not listed in the phone book. Only a few numbers out of the ten thousand possible for that special exchange would be used as data lines. That meant that even if hackers knew that Company X was running an open computer on a hidden exchange, they would first have to find the exchange. If they tried to do it randomly, they would have ten thousand calls for each exchange tested. Most of the time it wasn't worth the effort.
There was a way to break the hidden exchanges. Bobby was deep into the phone system. If he monitored a number of Anshiser businesses, and one called into a hidden exchange, we would have it. I worked through our Anshiser research again, and isolated five hotels most likely to use regular phone lines to transmit reports. Bobby would watch them for a few days, and if nothing happened, we'd look at different ones.
While Bobby was working, I took off again, heading south through Kentucky and Tennessee, dipping into Alabama and Mississippi. I spent a day at Vicksburg, down on the river, painting, then turned south and into Louisiana. The idea of New Orleans was tempting, but I was known there. I turned back north through Arkansas and into Missouri.
Each night I'd do between a dozen and a hundred tarot spreads, figuring the possibilities. The Fool was back, and that was okay. After the tarot, I'd call Bobby for progress. There was none until the fifth night, when I put into a tidy little Ma-and-Pa motel on the edge of the Ozarks.
Got exchange.
Great.
Not great. Dipped in. Have very heavy security. No on-line help. Get zero. Think one-time codes. Think probes spotted.
Traced?
No. But guard up now.
One-time codes are essentially unbreakable. There is no pattern, and they are used only once. Sometimes the operators on opposite ends of a phone link literally have identical pads of words: one is used, then that piece of paper is ripped off and thrown away, and the next one is used. The words may be of any length, pulled at random from a dictionary. Or they may be lists of numbers produced by a random-number generator.
Our problems were compounded by what Bobby thought was individual call monitoring: when we tried to get in, it set off an alarm. They knew somebody was knocking on the door, and without the correct codes. They would be watching for us.
The next night we went back into the exchange, intending to proceed most delicately. It was empty. They had changed it again.
Unless we get codes we locked out. Watched Anshiser/Vegas Hotel data line, there was call-in call-back, enough data that may be two-way one-time codes, maybe simultaneous voice monitoring and clearance.
Okay. Hold probes. Need time to think.
Call when need us.
Sometimes, in high-security environments, a clerk from a remote computer, like that of Anshiser/ Vegas, would be brought into the home computer installation. He would go to a company-sponsored lunch and dinner with the home computer operators, often with a shrink or "enabler" present. The shrink would keep the conversation going, both in person and over internal telephones.
When the clerk returned to his remote site, he would call one of his new friends at the home base before each computer entry. They would chat until his identity was confirmed. Some companies even used voice-print analyzers as a backup. Only when the identity was confirmed would they begin the sign-on procedure. Since the procedure was a two-way affair, with conversation and code going both ways, it was essentially unbeatable. While there might be ways to read the transmissions, there was no electronic way to get inside and work with the computer itself. We would need a different route.
How good is access to credit computers?
Read-only or read-write?
Read-only.
Good access.
Need complete run on all Anshiser lower-level execs with likely computer access. Find worst credit, forward names.
OK. Tomorrow.
While Bobby was running the credit reports, I went back into the NCIC computers using the codes we'd stolen from Denton, the Washington cop. This time I wasn't looking for anything deep, just the standard rap sheets. And I wasn't looking for felonies, I was looking for sleaze. I came up with a half dozen possibilities. When Bobby sent his list of bad credit reports the next day, we had one match.
I dumped the car in St. Louis and flew to Miami the next afternoon. Our man, Phil Denzer, was in the book. There was no answer at his apartment up to eleven o'clock that night. I found his apartment on the map, in a complex in North Dade County, and the next morning drove up to talk to him.