Slashdot Mirror


Passwords Not Going Away Any Time Soon

New submitter isoloisti writes "Hot on the heels of IBM's 'no more passwords' prediction, Wired has an article about provocative research saying that passwords are here to stay. Researchers from Microsoft and Carleton U. take a harsh view of research on authentication (PDF), saying, 'no progress has been made in the last twenty years.' They dismiss biometrics, PKI, OpenID, and single-signon: 'Not only have proposed alternatives failed, but we have learnt little from the failures.' Because the computer industry so thoroughly wrote off passwords about a decade ago, not enough serious research has gone into improving passwords and understanding how they get compromised in the real world. 'It is time to admit that passwords will be with us for some time, and moreover, that in many instances they are the best-fit among currently known solutions.'"

232 comments

  1. job security by tverbeek · · Score: 5, Funny

    Sounds like job security for those of us who reset passwords for a living.

    Drat.

    --
    http://alternatives.rzero.com/
    1. Re:job security by Anonymous Coward · · Score: 0

      Sounds like job security for those of us who reset passwords for a living.

      Drat.

      Those are the key words: passwords won't go away until someone comes up with some sort of new [cheap] 'thingie' that can be reset whenever the user wants (it most also not be just a physical token, because it can still be stolen easily). You can't easily reset your fingerprints, retina etc. So when the bad guy finds a way of using your fingerprints (or other biometrics), there won't be anything that you will be able to do right away (except asking for your account to be locked) and hoping the bad guy is caught.

    2. Re:job security by hawguy · · Score: 4, Insightful

      Sounds like job security for those of us who reset passwords for a living.

      Drat.

      Better to reset a password than find that your fingerprint scanners can be compromised by silly putty or your retinal scanners can be compromised by a picture painted on the back of a marble and instead of resetting a password, you're replacing hardware.

    3. Re:job security by kdemetter · · Score: 4, Insightful

      Biometrics are a form of identification , not authentication.
      It should always be used in conjunction with authentication, not to replace authentication.

      It's still very usefull , because it saves time : you don't have to fill in your login id : the systems knows who you claim to be, and just requires your password to confirm it.

      So it can replace the userid , but never the password.

    4. Re:job security by Anonymous Coward · · Score: 0

      How to compromise the small slit style fingerprint scanners?
      I have a hard enough time remembering what part of my fingers were scanned and can't use more than half my fingers anymore because of that.
      Anyways, you'd need physical access to try the scan so you'd be able to boot up Konboot and hit "other credentials"

      Long live Kon! King of the Valley of the Gods!

    5. Re:job security by fish_in_the_c · · Score: 2

      This seems like a false dichotomy
      all of these are just ways of establishing a trusted relationship.
      ex: consider a system that requires passwords to be unique but after given a password uses it to decrepit a set of bio-metric templates and then authenticates the identity of the person using those bio metrics.

      in the end it is all about HOW strong and how expensive your security needs to be.
      If we could build a computer that was more accurate then your best friend at identifying you using multiple bio metrics ( voice, face, body, smell , DNA) would that be good enough?

      The system could still be made more secure , very cheaply by requiring you have a badge and know a pin.

      Bio metrics , are possibly the most natural way of establishing trust , but they are also the most expensive way.

      The have the added disadvantage that once compromised , they are very difficult to change.

      --
      âoeTolerance applies only to persons, but never to truth. Intolerance applies only to truth, but never to persons.
    6. Re:job security by kdemetter · · Score: 2

      I never said you need biometrics for identification, it's a choice.
      A badge requiring a pin is a very good example of identification and authentication used correctly.

      An advantage of biometrics could be that you don't have to worry about losing your badge. You always have your eyes and fingers with you ?
      Offcourse, there should always be a fallback where you can type your username, incase something goes wrong ( biometrics can fail to detect you , and a badge can malfunction ).

    7. Re:job security by Twinbee · · Score: 1

      I know, how about we skip having to enter the user ID altogether, and just reply on the password. It's usually a pain to enter TWO things for every single website out there. The password can easily be an extra 3-6 digits longer to make up for the security loss of a username. Heck, the password could contain the user name if they really want.

      --
      Why OpalCalc is the best Windows calc
    8. Re:job security by Anonymous Coward · · Score: 0

      This works as long as everyone chooses a unique password, or as long as there's some other way to uniquely identify a user (say, email address). Many sites already simply use email addresses and passwords rather than usernames and passwords. Would you want someone else who chose the same password as you logging into your account by accident? Probably not.

    9. Re:job security by Max_W · · Score: 2

      You always have your eyes and fingers with you ?

      Sorry to mention these sad facts, but there were cases of cut fingers to steal an expensive car with biometrics security, to get pension money instead of a dead man, etc.

      Biometrics are known to turn a trivial crime into serious one.

    10. Re:job security by magisterx · · Score: 2

      There are a fair number of people without fingerprints though. There is a genetic condition that will cause it as well as certain occupations/hobbies that will effectively sand them away (bricklaying is one amoungst several).

    11. Re:job security by Anonymous Coward · · Score: 0

      The have the added disadvantage that once compromised , they are very difficult to change.

      Like in real life. When drunken me has compromised my bio-ID and his actions are attributed to me, what can I do? Wear a mustache?

    12. Re:job security by Joce640k · · Score: 2

      If we could build a computer that was more accurate then your best friend at identifying you using multiple bio metrics ( voice, face, body, smell , DNA) would that be good enough?

      Nope.

      Any "something you have" system can be compromised. A secure system needs something else, eg. something you know.

      To put it in your context, you might fool your best friend visually but as soon as you open your mouth and start talking he'll know you're a fake because you won't have the basic social knowledge that he shares with his real friend.

      --
      No sig today...
    13. Re:job security by Joce640k · · Score: 4, Insightful

      Just think "Eyeballs on forks..." next time you believe biometrics solves anything.

      People leave a whole trail of biometrics behind them as they go through life - dropped hairs full of DNA, fingerprints on drinking glasses, etc. You can steal their biometrics just by following them around.

      Worse: If you steal their wallet they might notice it's missing but they won't notice you picking up a drinking glass after they leave a restaurant. You can steal their biometric identity without them ever knowing it.

      --
      No sig today...
    14. Re:job security by Anrego · · Score: 1

      I've always wondered how I'd fare with biometrics... my fingers are usually pretty damn chewed up from playing guitar. At a minimum it would introduce a lot of inconsistency.

      In general I think biometrics have a place in authentication as part of a multi-factor system. Using them on their own seems like a really bad idea as once someone steals an image of your fingerprints.. you can't exactly revoke them, as was said.. but they would add an extra block an attacker has to deal with.

    15. Re:job security by Anrego · · Score: 1

      Ideally the best system would confirm the something you know without you revealing it. Kinda like human PKI.

      Obviously such a system would be tremendously unwieldy .. probably requiring the user to do some kind of calculation in their heads.. but might be useful for ultra high security type applications.

    16. Re:job security by Anonymous Coward · · Score: 0

      For those that have very dry or chronically cold hands, at least hand biometrics is NOT "quick" by any stretch. If you are required to put your fingerprint on a sensor, unless you're unconscious and pulled over to the scanner, then this is more than enough and actually more secure than passwords/usernames (well, unless your password is greater than say 20 characters)

      Passwords, unfortunately, will be around for a long time for one simple reason, however... Accidents happen that remove other forms of identification. This is actually very specific but still happens. I work in healthcare and the medication distribution computers that spit out meds for patients use biometrics. This said, when you lose a finger to say something like infection and it just so happens to be your biometric finger, you need a password to reset things and make 'em right.

    17. Re:job security by swillden · · Score: 1

      Biometrics are a form of identification , not authentication. It should always be used in conjunction with authentication, not to replace authentication.

      It's still very usefull , because it saves time : you don't have to fill in your login id : the systems knows who you claim to be, and just requires your password to confirm it.

      So it can replace the userid , but never the password.

      Biometrics can be used for authentication as well, but only in scenarios where it's possible to ensure that the person authenticating themselves is not using any sort of prosthesis, and where the security of the data acquisition path, the verification engine and the template store can all be assured. In those scenarios, biometrics provide very strong authentication. But that basically requires that all of the infrastructure, including the scanner, be in a physically-secured facility, and that the scanning process be watched closely by trained security personnel.

      For most authentication contexts, biometrics don't provide authentication.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    18. Re:job security by Briden · · Score: 1

      even better, someone might see this message when setting up their account:

      'sorry, somebody else already has that password'

      oh, ok great, now go simply login with it :)

    19. Re:job security by kdemetter · · Score: 1

      You always have your eyes and fingers with you ?

      Sorry to mention these sad facts, but there were cases of cut fingers to steal an expensive car with biometrics security, to get pension money instead of a dead man, etc.

      Biometrics are known to turn a trivial crime into serious one.

      That will only happen, if you use biometrics to authenticate ( which is stupid) . Use it to identify , and there is no reason anyone should cut off your fingers, because they would still need your password. And as I said, biometrics can fail , so there should always be a fallback system.

    20. Re:job security by climb_no_fear · · Score: 1

      My local video store requires a fingerprint to borrow a DVD. As you may have guessed from my username, I love rock climbing. After about a dozen attempts to scan ANY finger, they gave up and generated a code for me ...

    21. Re:job security by climb_no_fear · · Score: 1

      Sorry, I meant each and every finger of course...

    22. Re:job security by Anonymous Coward · · Score: 0

      Heck, the password could contain the user name if they really want.

      That's just a minor UI issue. There's no reason why the UI can't just give you one field to type in, and then it would automatically split your entry into separate username and password components for transport.

      It's important to note that at the transport level, the username and password must be handled differently, if you want to maintain best security. One provides identity, and the other provides authentication. This difference requires two different technologies to be used for transport (if you want maximum security).

      Believe me, if it was technically possible to truly combine the username and the password into just one indivisible string (and still maintain best security), they would have done that a long time ago.

      I think the reason you see two separate fields (username and password) is because most people feel that's the cleanest way to do it. Yes, it's possible to use a single text field, but it looks like the consensus is that it's an inferior solution from a UI perspective.

    23. Re:job security by Anonymous Coward · · Score: 0

      Most of us do not use GUIDs as passwords and giving the user a "That password is already taken" error message would reveal too much information.

    24. Re:job security by oursland · · Score: 1

      Here's a howto on that topic. http://www.instructables.com/id/How-To-Fool-a-Fingerprint-Security-System-As-Easy-/

      I have also heard that if you swipe any finger enough times it'll eventually accept it.

    25. Re:job security by yanyan · · Score: 1

      my fingers are usually pretty damn chewed up from playing guitar

      You're doing it wrong.

    26. Re:job security by allo · · Score: 1

      identification with biometrics is easy to do, and securely this way. authentication is not.
      When your android identifies you on a photo, its okay. Yeah, this IS you on the photo. But when it authenticates you with the photo, all the hacker needs is a photo of you.

      so first the identification (userid) step.
      Then there needs to be an authentication step, which means, the device needs some clue, that the identified person really wants to do the action. The photo contains no "unlock please" clue, and it would be wrong to define the clues in a way a photo could express. Because you do not want somebody to be able to make a photo of your "unlock please"-Face. You want to give this instruction each time by yourself.

    27. Re:job security by jc42 · · Score: 1

      That will only happen, if you use biometrics to authenticate ( which is stupid) . Use it to identify , and there is no reason anyone should cut off your fingers, because they would still need your password. And as I said, biometrics can fail , so there should always be a fallback system.

      So the plan is that they'll beat the password out of you, and then they'll cut off your fingers, right?

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    28. Re:job security by Anonymous Coward · · Score: 0

      You are probably trolling, but on the minute chance that you are not, that's a lousy idea.

      Instead of the evil person having to get the right password matched to the right userid, you reduce it to them getting a right password out of all the passwords on the system. If there are a million accounts on the system, you've changed it from the attacker having to guess right password for a single account at a time, to having to guess the right password for a million accounts at a time - you've made the attacker's life a lot easier. Plus there is a good chance someone has been foolish enough to use a really weak password (like "password" :) ). With your idea, it only takes one person that foolish for the system to be penetrated.

      Also, imagine if you enter a password and happen, by chance, to pick the same password as someone else - suddenly you are authenticated as them. Oops.

    29. Re:job security by _0xd0ad · · Score: 1

      I caught that, and I was beginning to wonder how many of them you had.

  2. Whatever happened to passphrases? by koan · · Score: 1

    I thought that was the next big thing.

    --
    "If any question why we died, Tell them because our fathers lied."
    1. Re:Whatever happened to passphrases? by Millennium · · Score: 5, Insightful

      Yeah; I've got to say, the situation with passwords could be improved just by allowing more space for them. xkcd/diceware-style phrases just plain don't fit in most password fields, but they'd be easier to remember and more secure.

    2. Re:Whatever happened to passphrases? by Kenja · · Score: 1

      Would be easy enough to throw together a bit of code that took a long pass phrase and mathematically convert it into a 8-12 character pseudo random password. Then when you forget the password, just run the pass phrase through the code again to regenerate it.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    3. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      My bank for their online site, only allow 6 letters and 2 numbers in the pass

    4. Re:Whatever happened to passphrases? by Dr_Barnowl · · Score: 5, Informative

      The stupid part is that the limit on the password field is just a piece of UI.

      If they're doing it right, they're storing a hash of the password. The hashes are all the same size. You should be able to carry around a USB device that emulates a keyboard and types out the declaration of independence (without using enter) and use that as a password.

      Systems that limit the password to, say, 13 characters bug the crap out of me, because I often chose passwords that are longer.

      Systems that limit the password size because they are storing them as plaintext, should of course have their source printed out and ritually burned.

    5. Re:Whatever happened to passphrases? by ISoldat53 · · Score: 2

      When will developers allow spaces in passwords? If they were allowed it would be much easier to use a phrase as a password.

    6. Re:Whatever happened to passphrases? by Dr_Barnowl · · Score: 3, Interesting

      I just realized that my bank must be doing this (or at least using reversible encryption) because it uses the whole positional character schtick. Damn.

    7. Re:Whatever happened to passphrases? by marcosdumay · · Score: 2

      They are passwords. It is just that they are longer, and have less entropy per character. And our minds work better with them.

      But, besides that, they are just passwords.

    8. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0
    9. Re:Whatever happened to passphrases? by StevenMaurer · · Score: 4, Insightful

      The problem in the real world with XKCD/diceware-style phrases, is that English words become keys. You don't have 44 bits of entropy. Rather, the vocabulary of the average American is the entropy.

      In the XKCD example, for instance, the true number of permutations you have to check to brute force a password is: Size of Average Person's Vocabulary (about 25,000 words) - from which "correct" "horse" "battery" "stable" is selected - raised to the 4th power, or 3.906 * 10^17 combinations. That's not a huge amount for a password cracking algorithm.

      Add in that many words are going to be used far more frequently than others, and it really isn't much different than the "misspell and stick in an odd character" method. And it's actually worse than sticking an odd character or two somewhere in the middle of your password.

    10. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      A pass phrase is just a really long password. Just because you're delimiting words within the password using spaces really doesn't make it particularly special. It's still just one big long string of character data, and you can still include numbers, special characters, and cases sensitivity within these very long passwords.

      tl;dr Passphrases are not a new concept.

    11. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Yeah, some of the rules sites have a rubbish. For your bank, do you use: 1curtit2?

    12. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      run the pass phrase through 50k or 100k iterations of pbkdf, use the binary result as a PRNG seed for a function that randomly selects from an array of acceptable characters.

    13. Re:Whatever happened to passphrases? by 140Mandak262Jamuna · · Score: 2

      The problem is the most common password for techie site is "horse battery staple correct".

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    14. Re:Whatever happened to passphrases? by godIsaDJ · · Score: 3, Informative

      Actually that's not the way that works. They are using a Zero-Knowledge protocol.

    15. Re:Whatever happened to passphrases? by TheLink · · Score: 4, Informative

      You don't have 44 bits of entropy. Rather, the vocabulary of the average American is the entropy.

      In the XKCD example, for instance, the true number of permutations you have to check to brute force a password is: Size of Average Person's Vocabulary (about 25,000 words) - from which "correct" "horse" "battery" "stable" is selected - raised to the 4th power, or 3.906 * 10^17 combinations. That's not a huge amount for a password cracking algorithm.

      2^44 is 1.7592186 * 10^13, which is SMALLER than 3.906 * 10^17. So if you assume a 25000 word vocab you have MORE than 44 bits of entropy with the passphrases approach. It may not be impossible to crack, but it's harder than the stupid "hard to remember by normal people" passwords. Which is the xkcd example's point, which I guess assumes a conservative 3000 common word vocabulary.

      --
    16. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 1

      25000^4 is already as strong as 62^10, ie 10 alphanumeric characters. Not extremely secure, but more secure than most Joe Sixpack passwords.

    17. Re:Whatever happened to passphrases? by jellomizer · · Score: 1

      Correct Horse Battery Staple.
      <a href="http://xkcd.com/936/">http://xkcd.com/936/</a>
      I remembered the password, I had to Google the link.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    18. Re:Whatever happened to passphrases? by Cinder6 · · Score: 4, Informative

      My bank has a similar ridiculous restriction. 14 characters max, limited subset of symbols allowed. Because of this, my bank password is my least secure password, while it should be one of the strongest. I find it amusing that my WoW account is much more secure than my bank (greater password freedom + authenticator)--at least from an authentication standpoint.

      Mac users can use a program called 1Password to manage their passwords. It stores them in an encrypted file that you use a master password to unlock. And you can use browser extensions to have it automatically login to any site you've told it about, and it will generate passwords for you as well. It's the best solution I've found for having unique, strong passwords for every site or system you have a login for. Just make sure you choose a smart master password.

      (There's an iOS version, too, that syncs with the standalone app, so you have access to your passwords on the go.)

      Anyone know of something similar for other platforms? I'd like to get the rest of my family using stronger passwords than pet names or whatever they're using.

      --
      If you can't convince them, convict them.
    19. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Yeah; I've got to say, the situation with passwords could be improved just by allowing more space for them. xkcd/diceware-style phrases just plain don't fit in most password fields, but they'd be easier to remember and more secure.

      The "situation" could be IMMEASURABLY improved by letting go of the shitty paradigm of obscuring passwords as you type them. People would be far, FAR more likely (and able) to use more complex passwords if they could see what they are typing.

      Sure, we can spin all kinds of "what if" scenarios, but in the real world 99% of us 99% of the time are typing passwords with nobody looking over our shoulder. So all those failed logins, locked accounts, and helpdesk requests to unlock them are a legacy of stubbornness on the part of UI convention. Some of us are unfortunate enough to work for companies that require both ridiculous password complexity, AND on the order of a couple hundred logins every day. If I ventured a guess, I'd say I have at least 20 failed login attempts every day.

    20. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      You're actually giving the average American MUCH more credit than Randall Munroe was. With each word being 11 bits there, he was suggesting that the average American was selecting from about 2000 words. He was suggesting 1.7 * 10^13 combinations, which at 1000 checked a second is over 550 years. His "uncommon" modified word for the "don't use this" example is selected from a bank of ~64,000 words, which may be a tad high. Even being a little more generous than he was with the difficulty added by the modifications (say, bumping it up to 32 bits of entropy from his 28), the multi-word plain password is three orders of magnitude more secure.

    21. Re:Whatever happened to passphrases? by krinderlin · · Score: 2

      Last Pass for those of us in Android land. :-)

    22. Re:Whatever happened to passphrases? by jimicus · · Score: 2

      Systems that limit the password to, say, 13 characters bug the crap out of me, because I often chose passwords that are longer.

      IME the great majority of password limitations arise because of a very particular set of circumstances:

      1. A system is set up. For whatever reason, it doesn't let you have passwords with more than 13 characters.
      2. The head of IT reads an article concerning this system. This article notes that because of the way passwords are stored, the most secure password contains 8-13 characters. Before long, a policy is dictated stating that passwords must contain 8-13 characters for security reasons.
      3. A new system is brought in that integrates with the system in 1. This new system has issues with punctuation characters in passwords - it won't authenticate if your password contains any punctuation. So the policy gets an update. New passwords are purely alphanumeric, no punctuation.
      4. The head of IT moves on.
      5. The authentication is moved away from the system set up in (1); the new system doesn't have the 8-13 character issue. But the policy stays in place - nobody actually knows why it was brought in but it specifically says "for security reasons" so there must have been a good reason.
      6. The system in (3) is retired. None of the remaining systems suffer from the punctuation issue.
      7. Repeat steps 2-6 until you have a list of policies that effectively mean the dictionary of potential passwords that humans are likely to choose has about 100 combinations.

    23. Re:Whatever happened to passphrases? by FoolishOwl · · Score: 1

      It's a trade-off of length for memorability.

      One advantage of diceware-style passphrases is that you don't have to remember twenty or thirty random characters; you just have to remember four or five common words. Even if you don't actually memorize the passphrase, you need only glance at the display from a password safe to be reminded of "correct horse battery staple", and can easily type it, whereas you have to keep looking back at "bee0bdb64e1fd508a5983dccc66" to type it correctly.

    24. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Check out http://keepass.info/
      They have a version for PC, Mac, Linux, IPhone, Windows Phone, Android, BlackBerry and Palm. Also it's open source.

    25. Re:Whatever happened to passphrases? by Amouth · · Score: 2

      that doesn't quite address his concern on how the bank knows the value at a specific position in his password that should be stored in a one way hash where you need the whole password to verify the hash.

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    26. Re:Whatever happened to passphrases? by Joce640k · · Score: 0

      Yeah, that'll be easy to remember.

      Try following the XKCD link above before posting any more 'wisdom' on passwords...

      --
      No sig today...
    27. Re:Whatever happened to passphrases? by Joce640k · · Score: 1

      My bank has a similar ridiculous restriction. 14 characters max, limited subset of symbols allowed. Because of this, my bank password is my least secure password, while it should be one of the strongest. I find it amusing that my WoW account is much more secure than my bank (greater password freedom + authenticator)--at least from an authentication standpoint.

      I find it amusing that WoW doesn't block your account if you get the password wrong three times.

      Allowing unlimited retries makes WoW weaker than your bank even though they allow longer passwords.

      --
      No sig today...
    28. Re:Whatever happened to passphrases? by Joce640k · · Score: 1

      Systems that limit the password to, say, 13 characters bug the crap out of me, because I often chose passwords that are longer.

      Real security would come from making brute force impossible.

      eg. Make you wait half an hour if you get it wrong three times.

      Systems like that are way more secure than systems that allow really long passwords.

      --
      No sig today...
    29. Re:Whatever happened to passphrases? by Joce640k · · Score: 1

      Even better: Have a checkbox to turn on password hiding if you want it.

      --
      No sig today...
    30. Re:Whatever happened to passphrases? by Ihmhi · · Score: 1

      Who says the words have to be English? Who says the words have to be in the popular/modern lexicon?

      Onegaishimasu / Schadenfreude / Mnemonic / Abiogenesis

      Oh noes, look how vulnerable to dictionary attacks I am!

      That doesn't even count mnemonic devices, intentional misspeling, etc.

    31. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      that doesn't quite address his concern on how the bank knows the value at a specific position in his password that should be stored in a one way hash where you need the whole password to verify the hash.

      I suppose that depends on your threat model. If your threat model is "someone might compromise the banking server and download the password file" then you would want only hashed passwords on the server. If your threat model is "keyloggers/shoulder-surfers watching the password entry" then the positional character stuff makes it far harder to do.

      On balance, I guess they reckon that if someone compromises their banking server then they are toast, because the intruder can cause so much damage regardless of whether the login credentials are copied, whereas attacks on users and their terminals are more frequent and more defensible.

    32. Re:Whatever happened to passphrases? by davidshewitt · · Score: 1

      I found that lastpass works well for me. I use the same method you mentioned, memorizing a strong master password and then using the built-in password generator. It encrypts everything with your master password before uploading it to lastpass's servers. All encryption/decryption happens on your local machine, so lastpass.com cannot decrypt your passwords. The benefit to using lastpass is that you can use it on just about any browser on just about any operating system. It automatically syncs your passwords (in their encrypted form), so you can add a password on one computer and have it show up on another when you log into lastpass. I find this extremely useful, especially since my university requires me to change my password every 90 days! :( If you decide to switch, lastpass supports importing your passwords from a variety of other password managers, including 1Password.

    33. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Think that's bad? My bank enforces a 5-8 character limit, no special characters, just a-z 0-9 and can't start with a number. //Glad I don't keep money with that bank, just my mortgage.

    34. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      My bank for their online site, only allow 6 letters and 2 numbers in the pass

      Change bank

    35. Re:Whatever happened to passphrases? by gstrickler · · Score: 1

      Actually, the example is based upon a 2k (2^11) word vocabulary.

      And those calculations are without using any capitalization, numerals, punctuation, or symbols. That means it's nearly the minimum entropy of the pass-phrase. If many (a statistically significant number greater than 1/vocabulary_size) people choose the same word, and that is known (e.g. hackers publish a list of the 1000 words most commonly used in pass-phrases), then the entropy for a statistical attack will be somewhat lower, but it would have to degenerate significantly (by 11 to 16 bits, that is, by more than one word of the pass-phrase)) to be as week as the example password. Even if all 4 words were from the 512 (2^9) most common words, it's ~36 bits of entropy. To approach the level of the example password, the pass-phrase would have to contain something like one word from the 4 most common, plus one from the 64 most common, plus two more from the top 512. That yields 28-30 bits of entropy (since you don't know the relative positions of the common words). While that's not particularly unlikely given human nature, it's still comparable to a much harder to remember (and hard to type) password.

      Users can create even stronger pass-phrases by choosing at least one word from a larger vocabulary. And if you assume trivial capitalization may be used (first and/or last letter of each word), that's an extra 1.5-2 bits entropy per word, for an extra 6-8 bits entropy on a 4 word pass-phrase. If you allow (but don't require) non-trivial capitalization, mispelling(sp), numbers, punctuation, symbols, foreign words, made-up "words", and/or additional word counts, then users can create pass-phrases with much greater entropy that are still easy for that user to remember.

      According to studies, pre-school aged children in the US are exposed to 620-2150 words depending upon socio-economic factors, so even pre-schoolers have sufficient vocabularies for the above.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    36. Re:Whatever happened to passphrases? by vakuona · · Score: 1

      So true. it doesn't have to be that drastic though. However, a significant downside is that DOS'ing become too easy.

    37. Re:Whatever happened to passphrases? by Hatta · · Score: 1

      You might know that there's nobody standing over your shoulder. But it's hard to be sure you're safe from Van Eyck phreaking.

      --
      Give me Classic Slashdot or give me death!
    38. Re:Whatever happened to passphrases? by MobileTatsu-NJG · · Score: 1

      In the XKCD example, for instance, the true number of permutations you have to check to brute force a password is: Size of Average Person's Vocabulary (about 25,000 words) - from which "correct" "horse" "battery" "stable" is selected - raised to the 4th power, or 3.906 * 10^17 combinations. That's not a huge amount for a password cracking algorithm.,

      Isn't that only true if the number of words in the phrase is fixed?

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    39. Re:Whatever happened to passphrases? by gstrickler · · Score: 1

      To the GP, hiding passwords as they're typed is a great paradigm. Displaying them is a security risk. See below for a better option.

      To the PP, they should be hidden by default. However, outside of high-security environments, having a check box to display the password is a reasonable compromise. Not simply because people learn and memorize better with a combination of visual and kinesthetic feedback, but because lengthy and/or complex passwords are more prone to typing errors, so allowing a user to see the password when he suspects he's made a typo, or when he's having trouble logging in will reduce the number of invalid login attempts and the number of password resets required.

      However, such a feature needs to be implemented carefully, so there is no chance that the next user (or next login attempt) can click to see the previous password attempt. Done properly, it's a fairly minor security risk, because it's normally hidden, and the user can determine if there are people who may be able to see the screen before displaying it. Done improperly, it's a major flaw.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    40. Re:Whatever happened to passphrases? by illiteratewithdrawal · · Score: 1

      Mac users can use a program called 1Password to manage their passwords.

      I use and love 1Password for Mac too. A Windows version is also now available. Linux, unfortunately, isn't, but can still be accessed from a Dropbox account.

    41. Re:Whatever happened to passphrases? by AlienIntelligence · · Score: 1

      4. The head of IT moves on.
      5. The authentication is moved away from the system set up in (1); the new system doesn't have the 8-13 character issue. But the policy stays in place - nobody actually knows why it was brought in but it specifically says "for security reasons" so there must have been a good reason.
      6. The system in (3) is retired. None of the remaining systems suffer from the punctuation issue.

      In the Buddhist world, what you described is a zen koan called "Ritual Cat" (and other variants)

      http://users.rider.edu/~suler/zenstory/ritualcat.html

      -AI

      --
      For me, it is far better to grasp the Universe as it really is than to persist in delusion
    42. Re:Whatever happened to passphrases? by geminidomino · · Score: 1

      That comic has always made me curious: How does one determine "bits of entropy" like that? Every time it comes up and I see it, I start a google mine, but usually end up either going around in circles, or hitting a wall.

    43. Re:Whatever happened to passphrases? by arose · · Score: 1

      The relevant wikipedia page appears to have citations.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    44. Re:Whatever happened to passphrases? by allo · · Score: 1

      the xkcd is not quite correct.

      you have choosen three words? okay, your entropy is just wordlist^3. This is way less than 12^(26*2+10+15) (12 chars, alphabetic, uppercase, numbers, reasonable special chars).

      simple rule: you want to have a big number in the exponent, not in the basis. Adding one more special char to your alphabeth is better than adding one char from the alphabeth to the password.
      of course this only matters, when enough chars of the alphabeth are used, you can generate a lowercase-alphabetic password from a 100 char alphabeth, if you are doing it wrong.

      another thing to consider:
      imagine the rule "password needs to be 8 chars, at least one uppercase, at least one digit, at least one special char)

      password would have been 8^(chars in alphabeth)

      but now it is:
      5^(chars in alphabeth)*26*10*15 * number-of-permutations possible for placing the three fixed chars inside the freely choosable ones.
      (26 upper chars, 10 digits, 15 special chars)

    45. Re:Whatever happened to passphrases? by allo · · Score: 1

      argh, bullshit, the exponent and basis should be swapped, so you need to have the longer password, sorry.
      but still not from a common wordlist, or the bruteforce with "three words from a good wordlist" will get you soon.

      and another thing:
      a password up to 8 chars is x+x^2+...+x^8
      a password which MUST be 8 chars long, is just x^8.

    46. Re:Whatever happened to passphrases? by allo · · Score: 1

      do you still own a CRT?

    47. Re:Whatever happened to passphrases? by dog77 · · Score: 1

      Your on the right track with the UI being part of the problem.

      We should never give anyone our password, including the site were connecting to or our own computers which could have maleware.

      Instead passwords should be stored encrypted on a personal secure device with say a USB connector, whos software and hardware have been well audited, with a touch screen keypad for entering passwords.

      It could work in this way. With your browser you make a SSL connection to the site, the site challenges you, your browser sends the site's public key and challenge over encrypted connection to your secure device. Upon receiving the challenge, your device asks you if you would like to connect to site with this public key, on behalf of browser xyz with session id xyz, where browser is previously authenticated, and session id is a random id displayed by your browser. Then it asks you to enter the password/pin/fingerprint, or whatever security you have setup on your secure device. However before sending out its challenge response, the secure device sends its own challenge to the site, asking for confirmation that the site is really the same site you originally setup the password for. After getting the challenge response from the site, and verifying the site, the secure device sends the challenge response to the browser, and the browser forwards that response to the site, and then use of the site can go forward.

      This has a number advantages: 1) You never gave our your password to anyone, but instead a key is generated based on the public key of the site you are connecting to, and a random key generated by your secure device, and the generated key is encrypted to the site itself, so that only the site can see this.

      2) Additonal authentication over the existing signed certificate scheme is done. This does not protect the first time connection, but does protect additional connections made, which gives you a lot more protection in that all aspects of a given site must be compromised for you to get spoofed, in otherwords the site's private key, trusted cert, and the key you share.

      If for whatever reason you lose your secure device or it is compromised there will need to be a way to invalidate your accounts, and so that will require some kind of group of trusted 3rd parties such as bank, email, or whatever you choose. This might be another set of passwords, background questions, etc. but this is not something you are going to do every day.

      Also for additonal security, it would be nice for servers to be able to quickly see if a secure device has been compromised by auditing with the trusted 3rd parties when it is able to do so. The site could take the first quick measure of suspending an account, and then require the much more careful measure of reestablishing an account to its full capability.

      For first time connection to a site, there would have to be additional security measures, and that is where a 3rd party (or group of 3rd parties) make sense to help in that establishment of trust. Where your secure device could force authentication of a site with 3rd parties, and the site could force authentication of your secure device with 3rd parties, before you agree that you are both trust worthy.

      Might as well tie this secure device to credit cards as well, in that your secure device becomes your credit card.

      Perhaps what I just described could be better implemented in a new SSL like protocol using the secure device as a proxy setup by your browser.

      This would require an overhaul of websites, browsers, and so on, but it is about time we develop and industry standard for solving this nagging problem.

    48. Re:Whatever happened to passphrases? by dog77 · · Score: 1

      One other nice feature to add to the secure device, is being able to break an existing connection. So if maleware did compromise your browser, and once you logged out, the maleware kept the connection up, it could start pulling money out of your account. It would be nice to be able to break that connection by requiring periodic rekeying or in the case that the secure device is just a proxy then it would be as easy as being able to disconnect the connection at the secure device (like a safety valve).

      Also adding ability to audit the data over the secure connection by your secure device, looking for insertions would be another nice plus. This would be possible if your secure device was a proxy.

      Also another feature is a simple side band communication protocol that could be used for confirmations between the site and your secure device to confirm transactions between the browser and the site . Like do you really want to transfer the money to some account? In other words the browser would never see this confirmation, and so maleware would never be able to function.

    49. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Systems that limit the password to, say, 13 characters bug the crap out of me, because I often chose passwords that are longer.

      These don't bug the crap out of me. They scare me. Because.

      1. Either they don't realise that hashing algorithms don't care about the length of a password (i.e. they have no clue about how hashes work)
      2. Or there are limitations in their software. For example, they're storing a password in VARCHAR(13). Which, of course, strongly implies:

      Systems that limit the password size because they are storing them as plaintext, should of course have their source printed out and ritually burned.

      Your password is one of the most important things you own, and you're entrusting it to jokers who fall into category 1, or category 2?

    50. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      I use KeePass for the same thing. There's implementations for Windows, Linux, and Android. I keep the encrypted password file synched via Dropbox.

    51. Re:Whatever happened to passphrases? by geminidomino · · Score: 1

      It never occurred to me to check the wiki for "Password Strength". Very interesting. Thanks!

    52. Re:Whatever happened to passphrases? by Anonymous Coward · · Score: 0

      Check out KeePass for Windows and the KeePassX port for 'nixes (including OSX). They use the same heavily encrypted file format (great for a USB stick with binaries for the platforms you commonly use), and include features like user-configurable autotype for convenience, and password generation using random user input as a seed - most of my passwords are now 30+ completely random characters, because why not? 'Course I'm screwed if I ever lose the password database or forget the password, but that's what backups are for, and one good, memorable password isn't that hard to come up with.

    53. Re:Whatever happened to passphrases? by _0xd0ad · · Score: 1

      How many possible unique passwords can be generated using that scheme?

      Take the log of that number, divide it by the log of 2, and you have bits of entropy.

  3. Unclassified Military by imamac · · Score: 3, Informative

    In the unclassified areas of the military passwords are almost gone (at least for me) by using PKI and our CAC cards.

    1. Re:Unclassified Military by Anonymous Coward · · Score: 0

      Since no on else said I will say it "sounds like a bunch of CAC to me"

    2. Re:Unclassified Military by Anonymous Coward · · Score: 0

      I've been trying for years to get people to pronounce the A in CAC as "ah".

  4. But of course... by Kenja · · Score: 3, Interesting

    All biometric systems do is substitute a text string for a string of values gathered from the users defining characteristics. Its the same thing in the end, and you will ALWAYS want a password backup to any biometric system as, despite popular understanding, your biometric signature can change. The best hand scanners for example mesure blood flow and 3D characteristics using holographic imaging. Getting a cold can cause your fingers to swell and throw off the scanners. Wearing a ring can change your 3D hand scan. Etc, etc.

    --

    "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    1. Re:But of course... by HockeyPuck · · Score: 4, Interesting

      Try breaking your wrist and having your hand/forearm in a cast...

      Exodus' solution was for me to use my left hand, upside down in the scanner and retake the initial scan since they only use right handed hand scanners.

    2. Re:But of course... by shadowrat · · Score: 4, Interesting

      not to mention, many of them can be hacked in simplistic or macabre ways. a coworker was touting his new phone's biometric authentication and how it recognized his face. He claimed it used some new algorithm that couldn't be fooled by a picture. The claim seemed accurate since a printed picture of him could not unlock the phone. However, the phone happily unlocked when shown a picture of his face on my phone.

      I don't know why it works. Maybe the identification of a real face is taking lighting into account or something and a self illuminated photo on an lcd throws it off. In any case it could still be defeated with his severed head. Now, a password might be given up under torture, but nobody is going to get it by killing you.

    3. Re:But of course... by Dan+East · · Score: 4, Insightful

      And what happens if your biometric signature is discovered? Obviously not from the biological side, but the digital side. After all, it's just a number. Of course it would require a more technical exploit at the software level to utilize, but the big downside is you can't change that signature like you can a password (you've only got so many finger prints, or retinas, or whatever).

      --
      Better known as 318230.
    4. Re:But of course... by Anonymous Coward · · Score: 0

      I have Raynaud's disease. Yeah, if they go to hand scanners, they'd better provide warm water at the scanner or else those hand scanners are going to cause me a lot of access problems.

    5. Re:But of course... by Nixoloco · · Score: 2

      In any case it could still be defeated with his severed head.

      That is macabre. I would think just tying him up and holding the phone up to his face would work just as well, or putting a gun to the back of his head, or if you must kill him I don't think removing the head is actually necessary. But hey, different strokes for different folks ;)

    6. Re:But of course... by Anonymous Coward · · Score: 0

      Sounds like a ADA lawsuit just waiting to happen.

    7. Re:But of course... by shadowrat · · Score: 1

      sure sure, you can do that, but obviously, the best solution is to then have his face removed and surgically grafted to your head. If you have the time, you can also have your old face grafted back on him. Then walk away with a clear conscience and a phone you can unlock at will. The chances of him breaking out of prison after being arrested for your crimes, convincing just one trusted friend that he is not you, hunting you down, and ultimately unlocking the phone are practically nil. He doesn't have the face that unlocks it anymore!

      well, things don't always play out so well. sometimes you don't have time to recover from such a procedure, or you can't afford the staff and equipment to pull it off. Maybe you just killed him and need to get away and collect your thoughts. Don't lug the whole body around, that's just silly.

    8. Re:But of course... by Anonymous Coward · · Score: 0

      Probably checking for an IR reflection off of the cornea to determine "liveness". Your phone screen probably reflected back enough IR to fool his app.

    9. Re:But of course... by Aighearach · · Score: 1

      In any case it could still be defeated with his severed head. Now, a password might be given up under torture, but nobody is going to get it by killing you.

      Once the password (or head) is given, there is no need to keep you alive. It is the future hope that you will reveal the password that keeps you alive... and keeps them torturing you.

    10. Re:But of course... by Anonymous Coward · · Score: 0

      After all, it's just a number.

      So true.

      How about I just replace some DLL with an unauthorized version that reads the retina scan image from a file instead of from the camera?

      You think you have a solution to my DLL hack? Well, maybe you do. But I have 1000 other types of hacks I can explore.

      Your little biometric ID scheme is exactly as secure as the effort to try preventing "unauthorized" DVD playback. In both cases, their security depends exclusively on trying to prevent the user from moving data from point A to point B.

      Biometric schemes are as effective as a $5 padlock. It discourages casual users from compromising security, but it provides absolutely no defense against someone who's armed with professional tools.

  5. Passwords make my brain hurt by na1led · · Score: 3, Insightful

    It's bad enough having to remember all my login names, but when sites don't like your password because it doesn't have Caps, or long enough, or a number in it. Forcing me to come up with a half dozen passswords to remember.

    --
    -- By all means let's be open-minded, but not so open-minded that our brains drop out.
    1. Re:Passwords make my brain hurt by Capt.DrumkenBum · · Score: 2

      Passwordsafe can be your friend.
      http://passwordsafe.sourceforge.net/

      --
      If I were God, wouldn't I protect my churches from acts of me?
    2. Re:Passwords make my brain hurt by John+Hasler · · Score: 1

      Forcing me to come up with a half dozen passswords to remember.

      Only a fool uses a single password for multiple sites. Write the damn things down as Bruce Schneier tells you.

      As for your brain hurting, that's exercise. No pain, no gain.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    3. Re:Passwords make my brain hurt by _0xd0ad · · Score: 1

      Oh, please. Wake me up when you have real problems, such as sites which don't like your password because it is too long, or does have some special character in it, but only tell you this after you try to set a password they don't like. Or, worse, says the password is invalid but still doesn't say which characters it doesn't accept. Or, or worst of all, lets you set an invalid password and then you can't log in.

      (password rules are usually pretty clear, but "secret questions" == extra passwords, and they are almost never clear on how long, or what characters are allowed)

    4. Re:Passwords make my brain hurt by arose · · Score: 1

      Or, or worst of all, lets you set an invalid password and then you can't log in.

      Been there, done that. This particular abortion of an authentication system required a special character, but only out of a small set. Long story short I set up a password with a special character outside of the range without a glitch. The login page actually respected that limitation...

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  6. Partial security by Anonymous Coward · · Score: 3, Insightful

    ...but still better than none.

    A proper security system is one that has tests for who you are, what you know, if you are under duress, and potentially if you should even be there that day.

    Such a security system is hard to make, in the simplest form it has a biometric component, two passwords (one for regular use, one to act like the proper password but alert security), and is hooked up with the scheduling system (not to lockout, but also alert security). This is reasonable for high stakes facilities, but sufficiently cumbersome that it gets in the way of getting things done for things like PC login and on-line transactions.

  7. Stop limiting password length by Pope · · Score: 5, Insightful

    Why does web site x have an 8 character length limit, alphanumeric only?

    Why does web site y have more allowable character types, but minimum of 5 chars, max of 18?

    Relevant XKCD: http://xkcd.com/936/

    Remember, you can't solve for the parts of a pw, only the whole thing in one go.

    --
    It doesn't mean much now, it's built for the future.
    1. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      If, by some other means, you have determined a password's length, you'll have a lot more luck cracking it if it's 3 characters rather than 30.

    2. Re:Stop limiting password length by MagicM · · Score: 5, Informative

      Steve Gibson from the Security Now podcast did a lot of work in this arena and found that the password "D0g....................." is harder to break than the password "PrXyc.N(n4k77#L!eVdAfp9". He makes this very clear in his password haystack reference guide and tester: "Once an exhaustive password search begins, the most important factor is password length!"

    3. Re:Stop limiting password length by hawguy · · Score: 4, Interesting

      Why does web site x have an 8 character length limit, alphanumeric only?

      Why does web site y have more allowable character types, but minimum of 5 chars, max of 18?

      And why won't they tell me what their password restrictions are until I've failed 3 times and need to reset my password? I use the same (or similar) password at all non-important sites (discussion forums, etc, not anything that involves a credit card, bank account, or personal email). If they'd just post their password requirements when I'm entering the password (or at least after the first time I mistype the password), I'd be able to remember what password I used.

      I can't believe hiding the password requirements makes life any harder for a hacker (who could just create a dummy account to see the password requirements).

    4. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      Sadly that isn't true in many cases. Look no further than the NT password scheme which can be cracked in halves.

      This is also quite often used in hardware attacks. There is someone through either leaked information, or modification that allows partial verification. I believe this is one of the methods that was due to break the Xbox 360.

    5. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      Of course, if they prioritize long strings of repeated character (which is a thing that is done), that long string of periods doesn't look so good anymore.

    6. Re:Stop limiting password length by Dan+East · · Score: 2

      Everything is migrating towards mobile devices, or at a minimum, some degree of accessibility from mobile devices. Longer, more complex passwords are even less conducive for use / convenience on mobile devices than computers with full keyboards. So I believe people are going to trend in the exact opposite direction - shorter passwords because they are easier to enter on mobile devices.

      --
      Better known as 318230.
    7. Re:Stop limiting password length by Pope · · Score: 1

      And why won't they tell me what their password restrictions are until I've failed 3 times and need to reset my password?

      Bad design, pure and simple.

      --
      It doesn't mean much now, it's built for the future.
    8. Re:Stop limiting password length by MagicM · · Score: 4, Insightful

      From the link:

      The example with "D0g....................." should not be taken literally because if everyone began padding their passwords with simple dots, attackers would soon start adding dots to their guesses to bypass the need for full searching through unknown padding. Instead, YOU should invent your own personal padding policy. You could put some padding in front, and/or interspersed through the phrase, and/or add some more to the end. You could put some characters at the beginning, padding in the middle, and more characters at the end. And also mix-up the padding characters by using simple memorable character pictures like "" or "[*]" or "^-^" . . . but do invent your own!

        If you make the result long and memorable, you'll have super-strong passwords that are also easy to use!

      The goal is to prevent brute-foce hacking of your password, and the way to do that is by lengthening it. If you pick some long padding and add that to all your passwords, brute-force hacking it becomes prohibitively hard.

    9. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      Ah, yes, this is the stupid site that only gives me 6 characters for the password. Well, I'll reset my password, back to exactly what it was before since reminding me that their rules are stupid is all I needed to know to remember the password.

    10. Re:Stop limiting password length by Arrepiadd · · Score: 1

      Of course if that's the root password for the company's server and you type that close to someone else it won't be that difficult for them to find out.

      If your attacks only come from someone who knows nothing about the password, that theory works fine. If they saw you typing a three letter word and then put a bunch of dots after "PrXyc.N(n4k77#L!eVdAfp9" seems "slightly" better.

    11. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      No, thats what happen when programers create the security instead of security people. This is the same as having security as an afterthought.

    12. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      simple memorable character pictures like "" or "[*]" or "^-^"

      I've always liked (.)(.)

    13. Re:Stop limiting password length by Ambvai · · Score: 1

      My favorite requirement was exactly 8 characters, one of which must be capital, one of which must be a symbol, one of which must be a number, none of those three may be in the first or last position, and it had to be changed every month.

    14. Re:Stop limiting password length by swillden · · Score: 1

      From the link:

      The example with "D0g....................." should not be taken literally because if everyone began padding their passwords with simple dots, attackers would soon start adding dots to their guesses to bypass the need for full searching through unknown padding. Instead, YOU should invent your own personal padding policy. You could put some padding in front, and/or interspersed through the phrase, and/or add some more to the end. You could put some characters at the beginning, padding in the middle, and more characters at the end. And also mix-up the padding characters by using simple memorable character pictures like "" or "[*]" or "^-^" . . . but do invent your own!

      If you make the result long and memorable, you'll have super-strong passwords that are also easy to use!

      The goal is to prevent brute-foce hacking of your password, and the way to do that is by lengthening it. If you pick some long padding and add that to all your passwords, brute-force hacking it becomes prohibitively hard.

      Unless the attacker guesses that you're padding your passwords. In that case, even if the attacker doesn't know what your padding character is, or exactly how many times you're repeating it, the brute-force complexity only increases by a small amount.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    15. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      > the brute-force complexity only increases by a small amount.

      lolwut?

      between lowercase, uppercase, numbers and common symbols, you're looking at about 88 possible choices for a padding character (depending on keyboard language).

      so assuming the attacker knows that the password will only contain one kind of padding character (and not any sort of repeating pattern), and that the number of padding characters is 10 or less, that means they have to try an additional 880 variations for every single password they want to test.

      in what universe does a nearly thousand fold increase count as "a small amount"?

    16. Re:Stop limiting password length by swillden · · Score: 1

      in what universe does a nearly thousand fold increase count as "a small amount"?

      The universe where $2.10 per hour buys an Amazon EC2 instance capable of computing nearly four billion hashes per second. A thousand-fold increase only matters if the base problem, before the increase, takes non-trivial time.

      Also, if a thousand-fold increase is enough to be worth doing, you can get it much more easily just by adding two characters to your password. 88^2 = 7744.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    17. Re:Stop limiting password length by bertok · · Score: 1

      There's a really good reason, and it should scare you: they're storing the password in clear-text instead of its hash, so the length is important.

      Banks and other such organisations are likely to have some old crappy database running on a mainframe that was never really designed for "web" use. It may not even be possible to add new columns! What they do instead is take an existing unused column that takes a reasonably large text field, and stuff everything in there as a delimiter separated string. This is why they have to enforce a maximum password length, and why many sites also prevent you from using certain characters in passwords.

      It's retarded, it's crazy insecure, and ironically it's a problem that affects the most important systems and data.

    18. Re:Stop limiting password length by Anonymous Coward · · Score: 0

      This.

  8. CAC still uses passwords by tepples · · Score: 2

    Wikipedia's article about the CAC makes it out to be some sort of smart card, the same form factor commonly used along with a PIN for debit card payment in some countries. The CAC doesn't really remove passwords at all; a PIN is still needed.

    1. Re:CAC still uses passwords by imamac · · Score: 1

      True, it still needs a PIN. But that CAC works for every DoD website. As opposed to remembering hundreds of login/password combinations.

    2. Re:CAC still uses passwords by Anonymous Coward · · Score: 0

      So all we need to do is use the Govern'ment to handle all authentication. Because... if we can't trust Uncle Sam, who can we trust?

    3. Re:CAC still uses passwords by imamac · · Score: 2

      Of course not. But if you get multiple trusted organizations to to issue PKI certificates to load on to a smart card and every person to buy a smart card and reader for their computer and then get every website to add in the functionality...problem solved. Somebody make it happen.

    4. Re:CAC still uses passwords by Anonymous Coward · · Score: 0

      I'm not sure, but wouldn't that suffer from the same issue as password reuse? It works for DoD because all accessible sites are trusted. I would be concerned if a private site, for instance, allowed access via CAC cards. That would be a huge vulnerability, if they fooled anyone into using it.

    5. Re:CAC still uses passwords by Dr_Barnowl · · Score: 1

      Estonia managed it (for government purposes).

    6. Re:CAC still uses passwords by Anonymous Coward · · Score: 0

      But what is ALSO needed is the CAC card, or the digital certificates on the card. Now someone wishing to compromise the account can't simply know/guess your account name, and compromise the password.

    7. Re:CAC still uses passwords by imamac · · Score: 1

      I certainly would not use a DoD CAC on any non DoD site. Maybe I haven't thought this out well enough, but I would think there would be a way to civilianize this to work on the internet in general. (i.e. the websites would use the trusted issuers to verify the identity certificates and would not have access to actually view the certificate.) But, I'm not an expert on the topic.

    8. Re:CAC still uses passwords by Anonymous Coward · · Score: 0

      Not if the site only had the public key part of the certificate. If it worked by them requiring you sign some random string with your private key, then they authenticate it against your public, they never know what your private key is. The only problem here, is that they have to authenticate that you are who you say you are, and that your public key wasn't being changed with a MITM attack; but that's still present in password schemes.

    9. Re:CAC still uses passwords by s.petry · · Score: 1

      True, it still needs a PIN. But that CAC works for every DoD website. As opposed to remembering hundreds of login/password combinations.

      That has nothing to do with CAC, but rather how the authentication is propagated between sites. LDAP is the norm, multi-master with TLS connections between hosts and no, it's not crAptive Directory.

      Cards would allow auth with either a PIN or a complete password, depending on the client set up. Most legacy systems would only be able to get your log in name from the card if they could use the card at all. Many times, you are only accessing a console with the card.

      Long story short, Passwords are not going away. Legacy systems will be around for a long long time, and that is the biggest driver to keep them.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    10. Re:CAC still uses passwords by tepples · · Score: 1

      Which means every computer you use will need a reader for the card. Outside the DOD, and especially at home, that won't happen any time soon.

    11. Re:CAC still uses passwords by c++0xFF · · Score: 1

      The true benefit, I think, is a move to two-factor authentication. Something you have (the card) and something you know (the PIN). Biometrics would serve as the third factor (something you are), but I don't now if this is used for authentication.

    12. Re:CAC still uses passwords by Anonymous Coward · · Score: 1

      I have a tolerable 99% solution. Everyone in Europe has a Chip&PIN credit card. There are only a few huge banks. If they would issue Chip&PIN cards in the US (smart move anyway) and provide a trusted public key store for their issued credit cards, then you could trust the (acceptably evil but financially liable) bank to provide the public key for the credit card your customer is using to authenticate a transaction, Which they'll do anyway, since most are financial transactions anyway. Since most of the loss due to password compromise is through credit card fraud anyway, this addresses that problem directly. If you want to use crypto-tokens to do logins for your site, then you get through a trusted means the bank's public keys, use that to authenticate your conenction to the bank's public key server, and use that public key to verify that you're talking to a valid credit card. the CAC card readers are $17 retail and every keyboard and laptop in the DOD comes with it built in, so the technology is in mass production and woudl be cheap. Oh yeah, if you're a bank, you've got a vested interest in doing this anyway, so that you've got data you can sell on what sites your client is visiting. Yes, it's a lot of trust in the evil banks, got it. Yes, they'll monetize that data, but that's the price of having a trusted crypto-system. And, more importantly, it will take a subpenoe to get the data out of the bank, v.s. giving that data directly to the government (only other plausible way to do it). This will also address some of the bank's security concerns.

  9. Hmmm... by Dripdry · · Score: 2

    Seems like a conflict of interest to me: "Oh, passwords are here to stay!" seems to be FUD designed to discourage people from innovating so that MIcrosoft can find the patent first (because it'll eventually supplant their password system and the IP birds will come home to roost).

    --
    -
    1. Re:Hmmm... by GameboyRMH · · Score: 1, Interesting

      No, passwords (or passphrases, just a long password really) will always be there because information that is only stored in your memory is the most secure.

      Biometrics are quite easy to force out of you, when the reader is even secure (see face & iris scanners being fooled by pics, fingerprint scanners being fooled by scanned or molded fingerprints). No such thing as a duress password with biometrics.

      Keyfobs can enhance the security of a password, but by itself is *less* secure than a password, because they can be physically stolen. Same reason you should use passphrases on your SSH keyfiles.

      And everything else is variations on the same theme, biometrics or stealable tokens of authenticity, that all suffer the same flaws. They can enhance the security of passwords, but by themselves are inferior.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  10. Securty. by fish_in_the_c · · Score: 4, Informative

    I have worked for years with security and authentication.
    there are three ways to establish trust. Something you have , something are , something you know.
    that will never change. and most any one of them can be compromised. thus it is better to build systems that use
    more then one.

    care keys ( something you have)
    thumb print ( something you are)
    password/ pass phrase/ etc. ( something you know) .

    all three together are more secure and more trust can be built by using multiple aspects but the easiest will be probably always be something you know.

    Think about it authentication before computers.

    Go to the bank ( hopefully the banker recognized you ( multiple bio metric) )
    do you have your checkbook / check card/ pass book?
    do you have a pin / password etc.

    it really won't ever get much better you can use more and more bio metrics but that won't stop fraud only make it more costly.

    --
    âoeTolerance applies only to persons, but never to truth. Intolerance applies only to truth, but never to persons.
    1. Re:Securty. by Anne_Nonymous · · Score: 5, Funny

      >> Something you have , something are , something you know.

      My brother-in-law's password oughta be assholeassholeasshole.

    2. Re:Securty. by PolygamousRanchKid+ · · Score: 1

      Still, some users will always find a way to muck things up.

      "Nothing can be made foolproof, because fools are so ingenious."

      care keys ( something you have)

      You'll lose it.

      thumb print ( something you are)

      Like, dead. "We have his key, but his thumb is decomposed, so we can't open it anymore."

      password/ pass phrase/ etc. ( something you know)

      You'll forget it.

      You want to have a truly secure system? Get rid of any humans in the system.

      --
      Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
    3. Re:Securty. by Laur · · Score: 2

      there are three ways to establish trust. Something you have , something are , something you know.

      This is incorrect, there are only two. "Something you are" (fingerprints, retinas, etc.) is really just another kind of "something you have". The only differences between biometrics and something like a physical key or access card is that biometrics are horribly insecure (how many objects have you left your fingerprints on today?) and nearly impossible to replace if they get compromised.

      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    4. Re:Securty. by Anonymous Coward · · Score: 0

      That's not a counterpoint, it's merely trivia. I don't WANT my system to have no security if I die.

    5. Re:Securty. by spasm · · Score: 1

      Mine BIL's is assholeassholenothing

    6. Re:Securty. by fnj · · Score: 1

      Secure and sure. Secure and sure. Not just secure. A system even the authorized user can never enter because it's too bloody hard to accomplish is busted, but it's still secure. DAMN secure.

    7. Re:Securty. by fnj · · Score: 1

      If your arm is eaten by a shark or your eye is poked out by a nail gun, you'll never be able to get a replacement fingerprint or retina pattern, but if you lose your access card and are able to talk the security officer into giving you another, you won't be fired for inability to do your job because you can't get into the site.

    8. Re:Securty. by aix+tom · · Score: 1

      That's another important aspect: What creates more problems.

      I have seen all hell break loose because someone was able to break into a system.

      But I ALSO saw all hell break loose because the only person who was able to get into a system was not available in an emergency, and there was no way to access the data otherwise.

      So for each specific case you basically have to decide which of the two is *more* important.

    9. Re:Securty. by John+Hasler · · Score: 1

      ...if you lose your access card and are able to talk the security officer into giving you another...

      Which is pretty much the same as talking the security officer into letting you use your other hand or other eye.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    10. Re:Securty. by fnj · · Score: 1

      All right, wise guy, can't argue with that - but if both arms are eaten off and both eyes are poked out ... ?

    11. Re:Securty. by SockPuppetOfTheWeek · · Score: 1

      So they're basically the same, but different. Good to know; I hope you'll keep sharing these insights.

    12. Re:Securty. by fish_in_the_c · · Score: 1

      This is incorrect. Something you have implies a non-perm object that you posses. Something issued to you for the purpose of securing trust between you and others. A prime example is your drivers license or credit card. or a letter of recrimination with some official seal.

      It is a distinct category from 'something you are' because 'what you are' is harder to change more often then not impossible, weather or not it is compromised.

      If your credit card is stolen it can be re-issued.
      If your finger prints are compromised they are very hard to change, which is why they need a different category.
      The reason for the different category is exactly the reason you specified, that the non-replaceable nature of the subject changes it's use in establishing trust significantly compared to a card or a pin/ password.

      --
      âoeTolerance applies only to persons, but never to truth. Intolerance applies only to truth, but never to persons.
  11. Get it right the first time? by tepples · · Score: 5, Insightful

    Good luck typing any password as long as "correct horse battery staple" correctly on the first time on a handheld device's on-screen keyboard.

    1. Re:Get it right the first time? by Anne_Nonymous · · Score: 3, Funny

      connectwhore'sbantertable

      Yup, works fine.

    2. Re:Get it right the first time? by hawguy · · Score: 1

      Good luck typing any password as long as "correct horse battery staple" correctly on the first time on a handheld device's on-screen keyboard.

      I have a much easier time typing long alphabetic passwords than I do alpha+numeric+symbol passwords.

      And how did you know my password was "correcthorsebatterystaple"!? I followed the XKCD comic *exactly* to generate a secure password, it should have taken you 550 years to guess it.

    3. Re:Get it right the first time? by PPH · · Score: 1

      The example given in XKCD http://xkcd.com/936/ appears to be calculating entropy based on the vocabulary space of the English language, not the character space of a random string of N symbols*. Therefore, the strength they calculate would not be diminished by applying a spell checker to your password input. A few small misspellings would be tolerated.

      In other words, your password would be that strong even if your input was misspelled but then auto-corrected. I could live with that.

      *Using the Wikipedia formula, for 44 bits of entropy, and a message length of 28, I get N = 2.97. This is much lower than the N = 26 for case-insensitive, random Latin alphabet string.

      --
      Have gnu, will travel.
    4. Re:Get it right the first time? by Anonymous Coward · · Score: 0

      And if that's still too easy, try it without hands and eyes!

    5. Re:Get it right the first time? by xenocide2 · · Score: 1

      Technically, you could have your phone autocomplete / spellcheck your password if such a scheme were used.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    6. Re:Get it right the first time? by Anonymous Coward · · Score: 0

      Swype lets me write in English words very easily. Things which aren't English words, though...much much more difficult.

    7. Re:Get it right the first time? by mapkinase · · Score: 1

      You know what's wrong with this? Having to type in password. Handheld devices actually is the area where biometrics should work.

      --
      I do not believe in karma. "Funny"=-6. Do good and forbid evil. Yours, Oft-Offtopic Flamebaiting Troll.
  12. Re:Duh? by hedwards · · Score: 4, Insightful

    That was my thought, biometrics is an interesting trick, but if they manage to compromise the system you have limited options for changing it. Most people only have 10 fingers and 2 eyes and if somebody manages to compromise on of those you very quickly run low on options. And that doesn't even include what happens if you lose an eye or a finger or if one is just badly damaged to the point of being unreadable.

    I remember seeing a bit of a BBC program years back where the guy was using biometrics for a safe but couldn't get in. It turned out that because he was wearing contacts that the sensor didn't identify his eye and the safe wouldn't open until he took the contacts out.

  13. Device security by dinodriver · · Score: 2

    As more and more of my "online" activities take place on the iphone instead of the computer, password management has become much easier. Other than bank accounts, all log in info is kept by the phone and I never have to log in to anything: counting on the password lock of the phone itself to keep my stuff private should someone pick up my phone. But someone could overcome my 4-digit pass key or observe it (I know my wife's because everytime she has trouble with her phone she asks me for help and so I witness her unlock it). What would really be better is if devices had bio-based locking features so that only their assigned users could open them. One big padlock for the house, so to speak, so that we can safely leave all the contents unlocked and easier to use.

    1. Re:Device security by Anonymous Coward · · Score: 0

      4-digit pass key

      Why not pick a longer one? That'd at least make it more secure: 4 digits is not very many at all, even to protect against key-it-in-by-hand attacks from a semi-determined attacker. I'd say go for 6 digits or so; it's still not too hard to remember, but is way more secure than 4.

    2. Re:Device security by Anonymous Coward · · Score: 0

      a 4 digit pass key is not strong at all with unlimited trys. If you limit the number of times a wrong password or pin can be entered before it is locked (for good) then it's not so bad. Take a pin on a token it can be 4 numbers if you lock it out for good after 4-5 bad attempts. This is still not as good as using a longer key / adding alpha characters but not as bad as unlimited attempts.

    3. Re:Device security by fnj · · Score: 1

      Which do you fear more? Making your passwords so easy to steal that someone robs you of everything? Or making your passwords so hard to retrieve that you effectively lose access to them and lose access to all of your own stuff? Choose one or the other. Think carefully. Hint ... it's a trick question. Hobson's choice.

    4. Re:Device security by Anonymous Coward · · Score: 0

      Not a "Hobson's Choice", but a False Dilemma: only two choices are considered, when in fact there are others

    5. Re:Device security by _0xd0ad · · Score: 1

      Take a pin on a token it can be 4 numbers if you lock it out for good after 4-5 bad attempts

      You discount luck.

      I've guessed the passcode combination on at least 2 electronic door locks in 2-3 tries. And neither was the room number or street address. The hardest part was remembering which numbers I'd just randomly pressed when the darn thing opened.

  14. Keepass by Anonymous Coward · · Score: 0

    I recommend keepass to my friends. I advise them to use unique and random passwords for every account. I only know two passwords. My login, and my keepass passwords. That makes the password problem much more manageable.

    Regards,
    Jason C. Wells

  15. Particularly relevant... by RogueyWon · · Score: 1

    There's particular relevance to this subject today in relation to the news (via Eurogamer) of a potential weakness in the password system protecting Xbox Live accounts.

    If MS can't refute this one quickly, I suspect it's going to get quite serious. Potentially "Playstation Network hack" serious.

  16. Re:Duh? by Joce640k · · Score: 3, Interesting

    Ummm...simple answer, Microsoft/IBM/rest of world:

    Start adding a "please generate a good password for me because I'm too ignorant to do it myself and I'll choose '123456' " button to your user interfaces.

    --
    No sig today...
  17. Timely Missive About a Credential Hack by djl4570 · · Score: 3, Informative
    http://www.theregister.co.uk/2012/01/13/sykipot_trojan_dod_smart_card_attack/

    A new strain of the Sykipot Trojan is been used to compromise the Department of Defense-sanctioned smart cards used to authorise network and building access at many US government agencies, according to security researchers. ... Chinese hackers have adapted the Sykipot Trojan to lift card credentials from compromised systems in order to access classified military networks, according to researchers at security tools firm AlienVault.

    1. Re:Timely Missive About a Credential Hack by Rich0 · · Score: 1

      How do you get card credentials using a trojan? The card's credentials should never leave the card if the design isn't brain-dead.

      Probably one of those almost-smart card systems...

    2. Re:Timely Missive About a Credential Hack by djl4570 · · Score: 1

      They don't. As I understand this the trojan/malware compromises the PIN and then uses card/PIN for unauthorized access through additional malware. There's more here: http://it.slashdot.org/story/12/01/13/2216218/sykipot-trojan-variant-stealing-dod-smartcard-credentials

    3. Re:Timely Missive About a Credential Hack by Rich0 · · Score: 1

      This is why smart-cards should not accept PIN input from any external device. The PIN input should be a keypad directly on the card itself. The card should display the authenticated hostname connecting to it on an internal display as well.

      People have already defeated security on terminals in numerous ways - they should be generally treated as untrusted. Now, if you're logging onto a fileshare you can't prevent malware from copying data off that fileshare once you've connected, but you can at least prevent it from accessing other resources that the user hasn't explicitly authorized by reusing a token.

  18. Reasonable by Flipstylee · · Score: 1

    Cause in the future, who knows? I might decide to remove the locks from my house...

    I enjoy my many barriers of common entry.
    My property is managed by my identity and that's me, If i'm (here), it's because i belong (here).

    Nowadays information is unlike everything around seemingly, in overabundance,
    And in high density, damning even, only considering what one can find on Facebook and the likes.

    Privacy? This is the USA!

    1. Re:Reasonable by Anonymous Coward · · Score: 0

      *bong noises* riiight on maan

  19. Learning by gmuslera · · Score: 1

    Even if we still use passwords, a lot of things had changed in the last 20 years, not so much in technology, but in culture. A lot could had been obvious or not back then, but now there is more awareness regarding requiring longer passwords, having harder to guess/bruteforce but easier to remember ones, giving alternate approachs like two-factor authentication, etc. Is like comparing the first cars with modern hybrid or electric ones, still are "cars", the basic scheme is still there, there are no flying cars everywhere now as predicted 30 years ago, but still a lot had improved.

  20. Re:Duh? by SJHillman · · Score: 1

    10 fingers is still 10 more than the number of passwords most people can remember. If course, you'd need all ten fingers registered or else the users that be would constantly forget which finger they used.

  21. Brainstorming Discussion Group by Anonymous Coward · · Score: 0

    Question. If there was some kind of online group, mailing list or forum dedicated to brainstorming alternatives to password authentication, would you participate? I wanted to create one for a while, but I'm not 100% sure how to promote such thing to get people of different backgrounds into that discussion.

  22. Re:Duh? by Capt.DrumkenBum · · Score: 1

    How did you know my password is 123456?
    Time to change it. qwerty should be a good new password.

    --
    If I were God, wouldn't I protect my churches from acts of me?
  23. Re:I disagree by GameboyRMH · · Score: 1

    Must be a big demand for granny camgirls...

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  24. No one's thought about usablity, etc? NIST by Anonymous Coward · · Score: 0

    I guess NIST is nobody.... (For those outside the US, NIST: National Inst on Stds & Tech, official US gov't agency.)

                    mark

  25. Stupid bastards by Rational · · Score: 1

    This is the kind of arrant bullshit that just begs to be disrupted to death. Smartphones were shit and the companies that were complacent with that state got murdered by Apple. Digital music distribution was shit - same thing. Authentication is in an absolutely dire state, and ripe to be disrupted in the same way, as soon as a company with a bit of vision and a pair of balls takes charge. Apple, Google? Fuck knows, but it's going to happen, count on it. "Shitty" is not a stable, long term state in technology - even Windows has been shamed into becoming halfway-useable.

    --
    "Be nice, veer left, and never stop thinking" Iain Banks - Walking On Glass
  26. 10 passwords to much? by Feyshtey · · Score: 2, Insightful

    Security built to accomodate laziness pretty much assures compromise.

    --
    "But we have to pass the bill so that you can find out what is in it,..." - Nancy Pelosi
    1. Re:10 passwords to much? by Anonymous Coward · · Score: 1

      How is this insightful? This is the equivalent of it has to be unusable to work. It makes no sense. The idea that security can be as close to transparent to the end user doesn't mean it has to be insecure. In fact I would argue that a system that doesn't give a users an opportunity to be lazy is more secure.

    2. Re:10 passwords to much? by jmactacular · · Score: 1

      I don't mind having the most complex secure password in the world. I just mind having to remember it and type it in. Everywhere I go.

  27. Two Factor Authentication by pwileyii · · Score: 1

    In my opinion, passwords are pretty much here to stay for the foreseeable future. The thing that I see changing is making the password a single item in an authentication scheme. Most of the major websites have two factor authentication methods available (think Google, Facebook, Paypal, etc.) and most of the banks that I use have methods of dealing with unknown devices connecting, via a series of questions, an email link, or a code sent to me out-of-band. We are certainly moving in a direction where the password is simply a single piece of information of many needed to authentication. Obviously, the sensitivity of the information will determine what kind of security is needed, but five years ago two factor authentication was only used in the most secure situations and now it is available on the most popular web sites.

  28. Anybody remember client-side digital certificates? by dmorin · · Score: 2
    About a million years ago (1997, maybe?) I worked for a financial company that wanted to implement client-side digital certificates. No more passwords! At a time when all the web stuff was coded in Perl making external calls to a C library that talked to something called a "SafeKeypr" box to generate the actual certificates, it was pretty darned advanced. That crucial bit of hardware in middle was so secure that it literally had several WarGames-style keys that all had to be inserted simultaneously for the thing to work. At one point when it needed to be debugged, the tech wouldn't even let me see how she cracked it open, she just took the whole box back to her lab. (Neat - just found a link to a book on the project I never new existed. I wrote that code ;)]

    And yet, here we are almost 15 years later still using usernames and passwords. Oh, well. Was a fun project. :)

    True story -- when the project launched we had a big event, with everybody gathered around the box to turn their keys. Then they all took their key and scattered off to wherever, what with the whole "must keep the keys off site and multiple locations" thing. What nobody realized is that the network center (we did our own hosting) had already posted plans for a scheduled power outage that weekend, and nobody'd connected these particular thoughts. So they cycled power in the room to do whatever it is that they did, and the box didn't come back online. Somebody contacted me. I told them to round everybody up to come back and turn their keys again. :)

  29. brute force in the Slepian-Wolf social network by epine · · Score: 3, Informative

    Brute force security needs to be evaluated under the assumption that a Russian botnet has compromised a large number of social networking sites, and gained three to five different clear-text passwords (of possibly no great importance) associated with the targeted user. They now also know--or strongly suspect--the identities of your financial institutions.

    Using commonalities of the exposed password set, the botnet bastards will attempt to model your personal password generation heuristic. Since they are not stupider than bricks, they might also assume that your bank password is similar, but fortified to the next level. Gaining some experience in cracking bank passwords, they'll soon have a model for that, too.

    My Thomas and Cover from 1991, which happens to be at hand, has chapters on "Jointly typical sequences", "Encoding of correlated sources", and "Source coding with side information". This last section makes reference to Slepian-Wolf encoding, which is kind of interesting. I hadn't spotted that before.

    On Slepian-Wolf compression, in memory of Jack Wolf

    Along with David Slepian, Wolf proved the Slepian-Wolf theorem: as long as certain conditions are met, files X and Y can be compressed to H(X,Y), even if the X server has no knowledge of file Y, and vice versa.

    This might not be precisely the right theory to apply to the breaking of password clusters, but the guy doing the math on that has probably read these papers.

    Way too little concern is placed on the independence of the passwords chosen, and this vulnerability increases rapidly with the proliferation of passwords used. I'm sure I have more than 100 passwords out in the wild, many held by hopelessly incompetent and untrusted internet discussion forums.

    Even a single compromised site can form a model of your password heuristic if you're duped into changing it often.

    It wouldn't surprise me that if everyone adopted the four word xkcd approach, that for many individuals, entropy per word is closer to seven or eight bits than eleven, where concrete nouns of five to eight letters predominate, and a further bias to concrete nouns that are visually active in the mind's eye, and 40% of all such passwords contain at least one animal word.

    That's where brute force would begin: assume at least one common animal word (four to five bits; since cat/dog don't make the cut, you'll be seeing a lot of parrot/leopard/zebra/unicorn).

    unicornprincesscastledragon

    I've cracked one already.

  30. IT is also enforcing worse password security by HannethCom · · Score: 1

    Where I work we have to change our passwords every 6 weeks. Microsoft even encourages draconian practices like this. Even though research shows that enforcing changing of passwords frequently leads to people using bad passwords, and quite frequently writing them down and leaving the written down copy at their computer.

    What really frustrates me is that our IT knows this, they wave it off as everyone uses bad passwords anyways. I try to use good passwords, but coming up with a new one every 6 weeks is difficult.

    That isn't to say that having a forced password change every blue moon is a bad idea, but more than twice a year for most people is too much. For quite a few companies twice a year might be too much.

    As with previous posters, I love how some sites only allow alphanumeric passwords, where others require special characters and you have the different minimums and maximums. Really drives me nuts how some sites have a maximum of 8 characters.

    --
    Microsoft, Apple, Google, Amazon what's the difference? All steal money from devs and control with walled gardens.
  31. Have you ever hacked MSDN and M$ by NSN+A392-99-964-5927 · · Score: 1

    Does anyone remember or even use Lynx anymore? These were the days in 1982 and I first had a Unix SLIP Serial Line Interface Protocol. That's right and dare I say it that was UN-31337 nothing was digital. it was only developers who illegally worked for GCHQ (deep packect inspection) British Telecom phorming. Well this is why we do not like the black boxen of all windows installations.

    AMEN!

    --
    All cows eat grass!
  32. Re:Duh? by Samantha+Wright · · Score: 3, Funny

    President Skroob: Did it work? Where's the king?
    Dark Helmet: It worked, sir. We have the combination.
    President Skroob: Great. Now we can take every last breath of fresh air from Planet Druidia. What's the combination?
    Colonel Sandurz: 1-2-3-4-5
    President Skroob: 1-2-3-4-5?
    Colonel Sandurz: Yes!
    President Skroob: That's amazing. I've got the same combination on my luggage.

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  33. Re:Duh? by Samantha+Wright · · Score: 1

    Observe, as actually making the joke magically garners mysterious karma points ... from beyond!

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  34. Re:Duh? by hedwards · · Score: 1

    Which is why things like KeePass and Lastpass exist. Plus if you add a site specific OTP to the authentication system that goes a long way towards securing things.

    Also, it's not just a matter of 10 passwords, it means that you can only have 10 ever. I suppose you could move to toes, but even that only buys you an additional 10, and on average person has slightly less than 20 digits total.

  35. Phew! "Passwords here to stay" by bareman · · Score: 1

    Don't sell your stock in the Post-It note company after all.

  36. Re:Duh? by lorenlal · · Score: 2
  37. Re:Duh? by Capt.DrumkenBum · · Score: 1

    That was my first thought too.

    --
    If I were God, wouldn't I protect my churches from acts of me?
  38. Re:Duh? by Anrego · · Score: 3, Insightful

    The big problem I see is revocation.

    Once biometric phishing shows up or a database gets popped, your prints are out there... and as was said, you can't exactly go out and get new ones.

    I've always been a fan of multifactor for stuff we want secure (banking mainly) .. yes you can copy someones fingerprint, steal someones keyfob, and snatch someones password .. but doing all three is tricky without them noticing.

    For stuff we care less about, passwords will probably be king for a long time, because anything more secure is also more of a pain ..

  39. So that's what makes it so easy... by Anonymous Coward · · Score: 0

    The problem with that is, that they can be stolen, or copied without the user's knowledge.
    It's pretty damn hard to get a password without the user being aware of typing it. ^^

    But hey, the more errors the terrorists (US military [Yes, I went there. Deal with it.]) make, them better for the free world.

  40. Passwords are like underwears! by antdude · · Score: 1
    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  41. Re:Duh? by Anonymous Coward · · Score: 0

    No.
    Never.

  42. It's time to reassess having passwords on paper. by Anonymous Coward · · Score: 0

    In the good old days I am quite sure there were a lot fewer and less sophisticated botnets, spillages of personal information and bank accounts being drained over the internet. If the threat from "unknown people online" was a lot lower then the threat from people around you were correspondingly the only real thing to care about, hence how the rule that you must never write down your password was etched into the marrow of civilization.

    Now people are virtually all behaving according to that rule, however subject to the their mental capacity. That means for example that they can only remember one password, so they reuse the same on every site. That makes them again subject to reusable personal data or just "robot hacks" (try a list of x million emails and passwords on y number of sites).

    I'm not saying that the threat from "people around people" have become any smaller, but it's possible that the threat from online sources have become relatively greater. In that case writing down passwords should be reassessed. Having just a sticky note with a key word like "Google - Paul" can remind people of the password "TAKEagoodsong!SONG!" which nobody in real life can guess and is far safer than any string of 8 random characters.

  43. Re:Duh? by fedos · · Score: 1

    Most of the humor in this punchline comes from the fact that Dark Helmet had just said that the combination was the kind that "an idiot has on his luggage".

  44. Re:Duh? by Joce640k · · Score: 1

    Publishing a comic isn't going to make people choose better passwords.

    People have had well over a decade years to learn about choosing passwords but they're as ignorant as ever.

    The only way forward is to take the choice out of their hands. Use the XKCD method if you want, just don't let the users do it themselves.

    --
    No sig today...
  45. Re:Duh? by Ambvai · · Score: 1

    A lot of people just don't think of passwords in an effective manner though; most people I know still subscribe to the 'Complex [to a human] and therefore difficult to remember is best' line of thought. Me, I just ended up switching to a line from a song that's 25-characters long and incorporates proper capitalization and punctuation. Easy to remember and pretty difficult to brute force!

  46. Re:Duh? by gstrickler · · Score: 1

    "please generate a good password for me and I'll write it down because I won't be able to remember it."

    FTFY

    --
    make imaginary.friends COUNT=100 VISIBLE=false
  47. All You Need to Know About User Security by sexconker · · Score: 1

    User security ALWAYS boils down to 1 question: How do I know you are who you claim you are?

    Passwords are the ONLY way to handle this.

    Biometrics are fuzzy at best, and in the end, it's just a biometric scanner sending a piece of information (password) to the authenticating host.
    Hardware dongles, keyfobs, or whatever else you call them are the same fucking thing. It's just another piece of information fed into the authenticating host.
    Security "experts" like to claim that these things are not "something you know", but are "something you have". But that's utter horse shit. It's just something that is difficult to know without having something else. And it's something that is EASY to know when you have it, even if you aren't the person who is supposed to know it.

    All of digital security, ever, boils down to a key sharing problem.
    You have to give someone a key when you first decide to trust them.

    Passwords are the most secure thing in the world in theory, because they're stored only in your brain.
    Passwords are much less secure in practice because people forget them, right them down, fall victim to phising attacks and keyloggers, etc. and authenticators tend to do stupid shit like get hacked, keep shit around in plaintext with little or no salting, etc.

    The only thing that needs to change about passwords is the mentality of users. Users need to realize that the trust has to be a two-way street. If you don't trust a site completely, you must assume they will spread your shit out or actively try to attack you.

    USERS must take it upon themselves to:
    Never use the same password in multiple places (this includes encrypting other passwords with a password).
    Never write a password down.
    Never use stupid passwords based on words.
    Figure out how to deal with an OH SHIT moment where you've lost a password. Unfortunately, this violates the other requirement.

  48. I always know who you claim you are! How? by Anonymous Coward · · Score: 0

    By how you always run when APK pwns U, lol -> http://it.slashdot.org/comments.pl?sid=2603836&cid=38661950

  49. Re:Duh? by Golddess · · Score: 1

    Good idea. Until you run across sites that require your password to be exactly 8 digits.

    Yes, you heard me right. Digits.

    --
    "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
  50. Re:Duh? by Anonymous Coward · · Score: 0

    Good idea. Until you run across sites that require your password to be exactly 8 digits.

    Yes, you heard me right. Digits.

    Exactly! You know what is even more crazy? My old bank's online password login was restricted to 6 letters or numbers (no more, no less, and certainly no symbols), and each letter corresponded to at least two other letters and a number, all case insensitive. You want to know why? Because they wanted people to keep their phone passwords and their online passwords the same! So if your password is 'BrUTal', you can also handily brute-force it with the numeric '278825'. Wow. Just wow.

    To be fair, I hear they did add some second-layer location verification questions later on (probably because they were getting murdered by script kiddies and grandma hax0rs). Like "we haven't seen you log in from this location before, can you please answer this security question for us?" then you got one of some couple 'password recovery' type questions that you had to answer before logging in. I dunno, I blew that joint a long time past, pretty much as soon as I tried to go online with them...

  51. Re:Duh? by sco08y · · Score: 3, Interesting

    Publishing a comic isn't going to make people choose better passwords.

    People have had well over a decade years to learn about choosing passwords but they're as ignorant as ever.

    The only way forward is to take the choice out of their hands. Use the XKCD method if you want, just don't let the users do it themselves.

    In many cases, you *can't* use the xkcd method because:
    a. the password field is too short
    b. the password checker rejects common words
    c. you can't see what you're typing when you enter the password

    The problem generally isn't the users' ignorance, it's the assholes writing the password system.

  52. Read the article, dammit by AlejoHausner · · Score: 1
    Please people, read the article in Wired. It points out something very simple and very important: since websites lock you after a handful of failed login attempts (or slow you down with captchas), brute-force cracking of passwords is no longer an issue! Strong passwords are a thing of the past.

    Feel free to use as simple a password as your system allows. No one will guess it.

  53. Password masking by tepples · · Score: 1

    But how can you know that Swype entered the correct English word if the password entry field covers it up with asterisks or other similar glyphs?

  54. Re:Duh? by oursland · · Score: 1

    How is this wrong? Even Bruce Schneier advocates this method. [1] Protecting little peices of paper is something everyone is already ingrained to do (think money), but remembering long strings of random numbers, characters and punctuation is not.

    [1] http://www.schneier.com/blog/archives/2005/06/write_down_your.html

  55. But do we need it? by Anonymous Coward · · Score: 0

    What is the chance that someone is going to come along and want to brute force my password?
    Woohoo - you can write a tweet from my twitter account, or update my facebook status. Or comment on whirlpool under my name. OR go through my lecture notes for uni - and my uni demand quite a lot of restrictions on our passwords! Is it worth worrying about security that much? In the grand scheme of things, not really.

    All my email accounts are linked to my phone so if someone picks up my phone, they can go through my emails anyways. Or my Facebook. Or my Twitter. Doesn't it then render having passwords on anything that can be saved to your mobile phone useless? I also don't use a password on my laptop because it has auto-login. Too much hassle having to put in a password every time I shut the lid and open it again, as I move from lecture theatre to lecture theatre.

      I use a basic common password on sites I don't really care about, because if someone finds my password, what can they really do? Less harm than what malicious software could do. Some websites are just over the top with restrictions for passwords, and I don't like the idea of memorizing a hundred billion passwords.

    I would much rather just have as minimal passwords as possible, and when I do have a password, it is for something important like my banking details. But even then, everything that runs through the bank has to be authenticated with a net-code from my phone. And as for sites that have credit card details, I refuse to let any website save my credit card details, as much as possible.

  56. The Secret Password is... by n6kuy · · Score: 1

    Oh, come on. you know it. Are you ready for Winchell-Mahoney Time?

    --
    If you disagree with me on social issues, then it's pretty clear that you are a narrow-minded bigot.
  57. Re:Duh? by allo · · Score: 1

    I did it, and then i lost the piece of paper. As i kept it in my wallet, i assume i lost it while paying. maybe some cashier got it ... maybe i even paid something with it ;).

    But there were no clues where the passwords are for, and i changed them as soon as possible, so it was no problem.

  58. Re:Duh? by gstrickler · · Score: 1

    I didn't say it was wrong, however, there are 3 flaws with the advice to write down your password:

    1. It based upon the premise that many/most systems are implemented using the currently in-vogue policies of complex, hard to remember passwords, and that you should/must use different passwords for each system. Both Schneier and the MS researcher (Jesper Johansson) whose comments at a conference inspired Schneier's blog post mention those limitations as the basis for writing them down.

    2. Both of those posts are very light on the topic of actually securing the written down passwords. Something which some other security experts have stressed, but which is frequently overlooked.

    3. People who do write down their passwords are not good at securing them.

    Unless you give complete instructions, including tips on protecting the written down password, then writing down passwords is not materially more secure than choosing easy to guess passwords. A far better recommendation is to use a password manager such as 1Password, KeePass or LastPass with a long, but easy for THAT user to remember pass-phrase.

    TL;DR: Writing down passwords is a recommendation about how to cope in a world of bad password policies, and it's an incomplete recommendation because users will leave their written passwords in easily found locations. A far better recommendation is to use a password manager such as 1Password, KeePass or LastPass with a long, but easy for THAT user to remember pass-phrase. Long term, we need sane password/pass-phrase policies.

    --
    make imaginary.friends COUNT=100 VISIBLE=false
  59. Choose your password by Anonymous Coward · · Score: 0

    Choose your password http://dazzlepod.com/uniqpass/

  60. Nothing new by Anonymous Coward · · Score: 0

    Passwords have been with us from the beginning of time in various forms.

  61. OpenID by Galestar · · Score: 1

    It does not eliminate all passwords, but it reduces the number of passwords one needs to remember. Given how many random websites and forums require a username/password these days, 99% of people have only 1 or 2 passwords spread across hundreds of sites - making passwords quite useless when one of those servers is compromised.

    Also, what happens when tomorrow's revolutionary new authentication method is invented? If all sites used OpenID, the change-over would be seamless - those who want to use the new method can do so, and the change only needs to take place in one location.

    In short, I am surprised they dismissed OpenID so easily.

    --
    AccountKiller
  62. roll ur own by peawormsworth · · Score: 1
    If u have access to perl, here is a simple program to generate passwords urself:


    #!/usr/bin/perl -wT
    my @charset = ('A'..'Z','a'..'z',0..9,qw(+ /));
    my $length = 64;
    my $iterations = 5;
    print join('', (@charset)[map rand $_, (scalar @charset) x $length]) . "\n" for 1 .. $iterations;

    I use this to generate impossible to remember passwords for all the sites and computers I access and router keys and stuff. I use a single passphrase to encrypt all of them and this works well in firefox by default (set a master password). I find it is possible for anyone to memorize a passphrase of 10 completely random digits in 2 weeks to a month (I have 4 in my head now). In that time, have the passphrase written down for reference and after that destroy it. Store a copy of all passwords externally on USB and make sure these are all protected using encryption protocols recognized by NSA for top secret documents. Never trust encrypting ur secrets with application based "encrypt" buttons... as these are usually made to be insecure so the company can protect their own butts. I am referring to fake encryption like when u click "OTR" in google chat or try to "encrypt" while using Skype.

    1. Re:roll ur own by SockPuppetOfTheWeek · · Score: 1

      Here's what I use:
      http://tinyurl.com/make-a-password

      Also, have a few yo-yo's to go with all those u's: yo, yo. Yo ho ho. Bottle of rum optional. That was exactly 5, did you count them? Just the number you needed.

    2. Re:roll ur own by peawormsworth · · Score: 1

      If u r suggesting that I use an online site in order to generate a password. I will tell u that this is highly insecure. It is kinda useless, because you have to trust that website is not storing the passwords it generated for you along with ur IP location into a database. To be use later against the websites. I think this is just a bad idea to be trusting others to create ur passwords... especially a website where u dont know who owns it. Ur better of just jamming the keyboard with ur fist a few times or rolling dice for a while. But if u have perl... the above script is easy to edit and run locally. If u dont have viruses then it is fairly safe. Also, if u use cut/paste and never type ur password, then it cannot be found from a keylogger.

    3. Re:roll ur own by Anonymous Coward · · Score: 0

      Go ahead and view-source and pretty the code. I made it deliberately easy. There's nothing going on that you should be concerned about.

      Anyway, even if it someone created a "password generator" that stored the password somewhere, a list of hundreds or thousands of high-entropy passwords without corresponding usernames or even knowing the website each password was used on... or even for that matter knowing it was used somewhere (say, add noise to the signal by copying about 10 passwords that you won't use before copying the one you will)... not terribly useful to a crook.

  63. Re:Duh? by _0xd0ad · · Score: 1

    It's pretty bad that I have to read the password requirements carefully and usually then view the HTML source to find out what the maxlen of the field is because the password requirements didn't define that.

  64. Captain Obvious here... by _0xd0ad · · Score: 1

    Someone can't steal your money just by looking at it.

    1. Re:Captain Obvious here... by oursland · · Score: 1

      That is true, but I still try to keep my money where you can't see it.

    2. Re:Captain Obvious here... by _0xd0ad · · Score: 1

      I won't argue with that. Cheers.