Subscriber Discussion
Use One Password Scheme For All Your Websites, Safe Or Unsafe?
Choosing passwords: You can do it "right" or do it "wrong".
Doing it right entails choosing different passwords for every site you need creds for, for some people that is easily over 100. You would need to store that list somehow manually or with a password manager.
Doing it wrong means using one password everywhere (or in my former setup three, one for banking, one for commerce, one for everything else).
Both have "pros" and "cons" that I am sure everyone is aware of.
I am using a new scheme now based upon trying to keep the pros of both with the cons of neither. Please Poke a Hole if you can!
New scheme is this: password consists of three parts, prefix, infix, suffix; The infix is some easily memorable but disjoint and unique phrase like "marTyism0zart", (not my real one), the prefix and suffix are derived from the site you are login into via some homemade transform that you always use.
Let's say my transform, a simple one for illustration, is just take the first two letters of the domain and for the prefix and the last two for the suffix, shifted by one letter. So ip=jq and vm=wn so the whole thing would be jqmarTyism0zartwn. But the key is to use make up your transform yourself. Then you can just remember one phrase and one transform and have unique passwords on all sites without storing them anywhere? Holes?

03/08/14 10:32pm
Because you are using a codified encryption method that does not require a 'key' be known/acquired by a receiving party, the only hole I can see (or maybe better, weakness) is if you are personally tortured to reveal the key (or code) that only you know.
Then it just becomes a pain threshold exercise.... :)

The password isn't as strong as it could be with, less characters:
Including more randomness and symbols helps slow down cracker programs. Including numbers in place of words can give Mneumonics to a seemingly random string. '5A1&ip$35' is easy to remember for me and only needs 9 digits to get the 100% mark.
Of course, dropping your password into a nonHTML5 'analyzer' is probably pretty stupid anyway.
Wait.
Who do you perceive the threat to be? I think your approach is likely to be effective against random attacks in isolation. The risk might be, for whatever reason, suppose two or more passwords are compromised by the same entity? Will they have what they need to understand all of your passwords?
Still, for most applications such as IPVM, the risk might be acceptable. For special applications such as banking, you might wish to use a different approach.
Personally I use two different transforms appropriate to the degree of protection required. My lowest ones can be broken with as few as two compromised passwords. My most critical ones that could cause me great damage if compromised (there are only a few of these) are unique, non-transformable, and must be memorized.
Also, password gatekeepers sometimes make demands that are incompatible with the transform. For example, length limitiations, special characters not allowed, etc. Does that bring you back to the password vault?
So, ... if you see even goofier posts than normal here on IPVM, I've probably been owned by the two-exemplar-crackable-transformed-password.
Best of luck with yours!

03/10/14 01:53pm
I tried making my passwords as difficult as possible, and got locked out of all my digital and online accounts. Now I just have seven or eight different long passwords, assigned randomly to online account access, and changed frequently.
My main protection against indentity theft, however, remains my terrible, horrible, awful credit rating. I wish I was kidding.
Begin Password Rant
Forgot password? Forgot password?
Why does it always say that? I'm not sure I have ever actually forgotten a password? I have forgotten which one I have used innumerable times. Usually because of some password restriction preventing me from using my ex-default password; my equivalent of 'hoochiemama'. So here are three suggestions for those software titans, who should quickly embrace my proposals and fast-track them into production.
After I have screwed up once please:
1. Show me a key of what the requirements are for a valid password, i.e., one number, one cap, and one beer, and not just the current ones, but the ones in effect when I chose it) (And no it won't help the hackers, they are the ones who know it already)
2. Let me ask a question or two. Like: is it the one than ends in z? (Advanced algorithims could play hot or cold. :)
3. Change forgot password to: Please let me help you recall your choice. (just cuz)
And no I don't think answering a question about a single letter will significantly affect security, since it would send a hint given e-mail and still lock you out after too many misses.
What am I overlooking or would this help only me?
End Password Rant
Newest Discussions
Discussion | Posts | Latest |
---|---|---|
Started by
Undisclosed Integrator #1
|
34
|
about 3 hours by Brian Robertson |
Started by
Russell Christman
|
2
|
less than a minute by Brian Rhodes |
Started by
Brandon Niskala
|
6
|
22 minutes by Mark Jones |
Started by
Brian Rhodes
|
10
|
1 minute by Undisclosed Integrator #4 |
Started by
Mark Jones
|
4
|
22 minutes by Mark Jones |