What's your online privacy quotient?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Cyberian

Diamond Member
Jun 17, 2000
9,999
1
0
YOUR PRIVACY QUOTIENT (HIGHEST POSSIBLE SCORE IS 100): 51

I'm too lax about passwords, but I don't do any online banking.
 

tennisflip

Golden Member
Sep 25, 2003
1,845
0
0
Originally posted by: Cyberian
YOUR PRIVACY QUOTIENT (HIGHEST POSSIBLE SCORE IS 100): 51

I'm too lax about passwords, but I don't do any online banking.


I think that's what brought score down, too. I keep several of the same passwords but they're uber uber complicated.
 

ClueLis

Platinum Member
Jul 2, 2003
2,269
0
0
60 for me. They should have also accounted for what browser people use as well, though.
 

DOSfan

Senior member
Sep 19, 2003
522
0
0
Ehhh.... I got a 52.

But then I never change my passwords.

I just change how they are entered.

My system is quite secure for low profile users (not that great for high profile users or corperations though). It isn't uncrackable, but it keeps the "script kiddies" out of my stuff. Here is my system:

Memorize a six digit number. I do not recomend the use of personal information, but it works well enough using the "dangerous stuff."

For example, if you want to use a kids birthday: 060603.

Now pick one of those digits and spell it out instead. ie. 060six03

Now you can mix and match capitalization, which digit is spelled out, more than one digit, etc. and all you have to remember is the six digit number, and what you did to it. Be careful with spelling out more than one digit. You might hit password maximum lengths. With only one digit you get a password length of 8-10 characters.

And for anyone thinking of hacking my shiat - my number does not involve my personal data at all. :p (And for really important stuff, I do not use this system. ;))
 

EyeMWing

Banned
Jun 13, 2003
15,670
1
0
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.
 

PowerMacG5

Diamond Member
Apr 14, 2002
7,701
0
0
YOUR PRIVACY QUOTIENT (HIGHEST POSSIBLE SCORE IS 100): 68

I think the fact that a few years ago my computer was infected with a virus, and hacked may have shown something. This is one of my favorite stories. About the time after the movie the Matrix first came out, some one took over someone in my houses comp, and put a screen similar to Neo's. It said "Knock, knock Neo". So then the person said which pill would I like, the red or the blue. So then I said, thanks for your IP address, time to call the FBI. The person swiftly left, and I was never bothered by that IP again :p.
 

trek

Senior member
Dec 13, 2000
982
0
71
Originally posted by: EyeMWing
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.
...or you could just mash the keyboard!

i got 56.
 

EyeMWing

Banned
Jun 13, 2003
15,670
1
0
Originally posted by: trek8900
Originally posted by: EyeMWing
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.
...or you could just mash the keyboard!

i got 56.

Not random enough. The letters are only grouped in one way on a keyboard, so it's possible to predict likely mashing combinations.