>Not if you give your username and passwords to websites. I feel like you don't understand this distinction all up and down this thread...

I've never given my username and password directly to websites, except for Etacts. For the other sites, I simply authorized them (through the Google interface) to access certain functionalities. Behind the scenes Google doesn't provide them with my password: https://www.google.com/support/accounts/bin/answer.py?answer...

They also put such sites on a list of that is accessible from your account. You can remove sites from that list at any time.

> Also, man, what is the point of DBANing your install?

Yeah, that's sort of unrelated. I've been planning a clean install for a while.

> you give your usernames and passwords to websites and then be surprised that they use them?

When THEY use them? No. When someone else does, yes.

Anyway, we have beaten this horse to death many times over.

You're giving your password to someone else. You don't magically get some guarantee that they are safe, that they won't be stolen etc. Yes, I know that oAuth perms can be revoked, that is the entire point and that's why it's dumb to give a site your credentials when better alternatives exist.

"I've never given my username and password directly to websites, except for Etacts." This is all about Etacts right? How do you expect someone to be accessing your account? You gave them your user and password. The point is, you hand out your username and password, it just makes you look silly to suggest that your account is being compromised by covert wifi sniffers (you are using encryption right?), etc.

I still don't understand why you need to DBAN to do an OS reinstall unless you are just using the term DBAN loosely.