POST 03.06

By the time I had finished writing and testing the programs, it was four days later. That was one of the most intense programming sessions that I had gone through in quite a while, so it was time to take a break. But first, I compressed, double-encrypted (128-bit), and emailed the programs to several of my bogus mail accounts. They would sit there safely as backup copies, just in case there were problems at home.

Before I started my "attack", I'd need to set up a safe house to run them from. Although I had lots of computing and communications power at home, it might be useful to run the initial attack from a different location. You don't crap in your own back yard. Use someone else's yard. That makes it harder to be found. And I didn't want whoever was distributing the viral router code to find me.

About a mile from my house was an apartment complex that was going through a change of ownership. They were looking for tenants, and there was a shortage of renters at that particular time. I looked at the complex, and saw that there was a vacant one at the back corner, and that there was a nice phone junction box right next to the vacant apartment. That would be perfect; I could set up some additional lines on some of the vacant lines that are in all phone boxes.

The apartment manager was happy to accept my cash deposits. Utilities were centralized and part of the rent, so I didn't have to deal with the local electric company. I'd need to set up some phone lines, but the wiring was already in the apartment, and I could find some active lines from the phone junction box outside the apartment. And the apartment was furnished, although the furniture was a bit worn, it was still serviceable. The apartment looked like it would work well: it was back in the corner, good access to the parking lot for my car, a quiet area, and power and phone lines were set up.

It was time to prepare the safe house for the attack.