66. But they did not account for realistic security measures - only 'standard' practice that does more harm than good. For example - I have one password for everything that I can afford to have compromised. Basically anything I don't pay for - like AT forums. I have 3-4 accounts on every computer with different logon passwords.
My passwords are created as follows:
CPU temp multiplied by time of day in minutes elapsed since midnight multiplied by percentage of total disk space used multiplied by the serial number on a random piece of hardware, divided by the net weight of the nearest food item, then divided by the network port number that the current computer is connected to. Convert this to hex and truncate at the max length allowed minus one third of third of that. Utilizing a random number generator, determine where to insert blank spaces in the password for later filling. Utilizing a printout of pi to the first billion digits (Or somthing like that) and a dart, determine which special characters to insert in the remaining spaces of the password !@#$%^&*() Of course, the pages of pi are randomly shuffled and one randomly drawn for use in the dart throw. That page is then burned. Then using an ultra-secret proprietary java app, I encrypt the password using a fairly unique character reordering algorithm and a random character replacement algorithm (The algorithm used is lost after being removed from memory - it isn't in the source)
This gives anyone trying to gain access to my systems the thrill of catching my simple 'sacrafice' password and then when they get to anything sensitive, they have to contend with a password generated via methods that they simply cannot break any way other than brute force. Combined with exceptionally long password lengths on many applications, this can translate into BILLIONS of machine hours to compromise an insignificant fraction of my network. I do not use instant messenger or email for 2-way communications unless the other party is either involved in a sale of some sort, or is encrypted (I tend to use Thawte [verisign] issued keys generated using false information so someone with a government ID or somthing can't just call them up and ask for the keys assigned to my SSN)
Of course I use different keys on different computers. All sensitive data is encrypted locally. All drives that I have ever used in a 'production' system are either destroyed (Disassembled, platters melted) if defective or Gutmann wiped if being sold.
But I'm not overly caucious about guarding things like my name, phone number and address. Anyone can just do a whois on my various domain names if they want that - I don't care. Why don't I care? Because I also have extensive security plans for physical access. Tresspassers WILL be fired upon after the first warning unless presenting a law enforcement badge (or were invited - at which point they will always be supervised)
If I had just a little less sanity and it were just a little less illegal, this place might even be wired for self destruct.
Oh, and I do not use virus protection software - I instead use common sense.