Slashdot Mirror


DARPA Wants To Kill the Password

jfruh writes Many security experts agree that our current authentication system, in which end users are forced to remember (or, more often, write down) a dizzying array of passwords is broken. DARPA, the U.S. Defense Department research arm that developed the Internet, is trying to work past the problem by eliminating passwords altogether, replacing them with biometric and other cues, using off-the-shelf technology available today.

58 of 383 comments (clear)

  1. There we go again by ArcadeMan · · Score: 4, Funny

    Kill and eliminate passwords? Violence is not the answer.

    1. Re:There we go again by Anonymous Coward · · Score: 2, Funny

      You say that now, but wait until you watch a password facehug and implant an embroy in your friend. He might seem fine then, but you'll be convinced when a password bursts out of his chest and start running around.

      Take off and nuke the entire website from orbit. It's the only way to be sure.

    2. Re: There we go again by Anonymous Coward · · Score: 4, Insightful

      We don't need to kill and eliminate passwords, we just need to modify them. The problem with passwords for the average user is the dizzying array of requirements from various websites (between 8 and 20 characters long, required to have upper/lower case and numbers, must have punctuation except "|~, etc.). I've never understood why passwords can't be sentences, like "I'm going to take my dog, Spot, to the park today." It's much easier to remember for the layperson and pretty quick to type once you've done it a few times. IANAC (I Am Not A Cryptologist), but I thought password strength was a function of length and potential characterset. It seems like everyday sentences would be the way to go since guessing it exactly right would be exceedingly difficult.

    3. Re: There we go again by Desler · · Score: 3, Insightful

      Only if you're dumb enough to let authentication program be suspceptible to such an attack. Dictionary attacks can be trivially defeated by rating limiting tries and after, say, 5 tries not allowing any more attempts for some cooldown period. No attacker is going to bother if they can only have 5 tries every 15 to 20 minutes.

    4. Re: There we go again by AC-x · · Score: 3, Informative

      Dictionary attacks can be trivially defeated by rating limiting tries and after, say, 5 tries

      Unless they have a copy of the password hash

    5. Re: There we go again by Anonymous Coward · · Score: 2, Insightful

      Dictionary attack on a >50 character password that includes capitals and punctuation in seconds? I want some of what you are smoking.
      Even if the attacker somehow knew that it was using sentances made entirely of valid words and not just random characters/words (how would he know this?) thats still one hell of a lot of words to attack.

    6. Re: There we go again by AC-x · · Score: 3, Insightful

      You seem to have no clue what a password hash actually is. The whole point of a cryptographic hash is it's one way operation; You can turn a password into a hash easily, but you can't turn a hash into a password without brute forcing it.

      Having a hash of a sufficiently string password is perfectly safe, in fact here's one now, bet you can't find the password from it. It's a basic SHA1 hash, not even salted: b6faa93a9e6ca445875c6b5511e2153bb51ef43a

      However if a chosen password appears in a password dictionary than you can cut down your brute force search space by so much it goes from taking years (even centuries) to crack a password to taking a few hours (sometimes minutes).

    7. Re: There we go again by Desler · · Score: 2

      Only if the passwords haven't been salted properly. Even then, a rainbow tables attack can also be thwarted by the same techniques I mentioned above. Allowing any attacker the ability to do 10s of millions if not a couple of billion (with powerful enough hardware) tries a second to brute force a password is just the height of idiocy. Using constant time password checking, rate limiting, cooldown periods and as a last resort IP bans makes you such an unattractive target that they usually just move on to some other insecure site.

    8. Re: There we go again by ncc74656 · · Score: 3, Informative

      I've never understood why passwords can't be sentences, like "I'm going to take my dog, Spot, to the park today."

      They can be, but it would be incredibly stupid to use something like that. A dictionary attack would crack that password in seconds.

      Are you sure about that?

      --
      20 January 2017: the End of an Error.
    9. Re: There we go again by AC-x · · Score: 4, Informative

      You probably shouldn't try to write about things you don't know about or understand.

      1. The industry accepted way to store passwords securely in a database is with a one-way, salted cryptographic hash (using as CPU intensive algorithm as possible).

      2. Many organisations have had database intrusions where these password hashes have been stolen (eg. eBay, Linkedin, LivingSocial etc.)

      3. When this happens (i.e. "they have a copy of the password hash") passwords can be cracked offline. Strong passwords are safe (too hard to brute force), but weak passwords can be found using a dictionary attack.

      4. Once the password is found offline a hacker can log straight in to the victim's online account with a single password attempt.

    10. Re: There we go again by AC-x · · Score: 4, Informative

      Hey Desler I really don't get you, you (appear to) know what a salt is yet you don't understand that an attacker would be performing the attack on the hash offline, with their own hardware. Rate limiting their own hardware would be, as you put it, the height of idiocy.

    11. Re: There we go again by wagnerrp · · Score: 2

      The point he was making is that with proper procedure, a hash could never be attacked offline. As soon as the hash database were compromised, all hashes contained therein would be invalidated. The attacker could brute force that database to their heart's content, and no valid passwords would ever result from it.

      This of course assumes the administrators are paying close enough attention to notice in short order when the database has been compromised, and that all users define a secondary means of contact through which to send a reset password. It also ignores the issue that most users use the same username and password across multiple sites, such that a pair compromised on one site and invalidated as described would still be valid on another site.

    12. Re: There we go again by AC-x · · Score: 3, Insightful

      Duh. Being Captain Obvious again?

      By your previous posts it seemed you needed things put in simple terms, especially since you claimed that 1) knowing the hash is the same as knowing the password (it's not) and 2) rate limiting could defeat offline password cracking (it can't). Do you stand by those claims?

      Of course, this is why you lock the accounts until the user resets the password. Poof that attack vector is now gone.

      That's no solution: 1) Relies on the attack being detected in the first place. 2) If the user has reused their password elsewhere this doesn't reset those too. It's also completely irrelevant to the question of being able to dictionary attack a password.

    13. Re: There we go again by morgauxo · · Score: 2

      "They can be, but it would be incredibly stupid to use something like that. A dictionary attack would crack that password in seconds"

      Really? How?

      First off, I would expect that a password cracking script's dictionary would include variations of single words and maybe combinations of 2. There are 11 words in that sentence. Anyone with such a password is such an outlier I can't believe any reasonable script today would be written to even try that!

      So, what if everyone used passwords like that? No doubt cracking scripts would change. But how is a dictionary attack going to work? They can't possibly put every parsable sentence of a language into a dictionary! The example sentence was 11 words. Even if we treated that as a limit, how many sentences can be made out of 11 or fewer words? Certainly there are far more possible 11-word sentences than there are 11 character passwords.

      And then there is punctuation. See the two commas?

    14. Re: There we go again by AC-x · · Score: 2

      Nope, because I never claimed that. You misunderstood my point and started falsely assuming things

      Yes you did:

      "But if the attacker knows the password hash that is not a dictionary attack. In fact, there would be no need for any attack at all." - No, you still need to attack (brute force) the hash to extract the password.

      "Yes, that's why you stop such attacks by rate limiting and cooldowns and then eventually just ban their IP if they are just obviously an attacker. If they can only have 5 tries every 15-20 minutes the attacker is going to give up unless the user's password just happens to be near the very beginning of the dictionary." - As written by you direct reply to a post about having the hash of a password, and is completely irrelevant if you have a hash.

      Of course it is predicated on knowing you've been attacked. I was pretty sure that would be quite obvious.

      The point is having a strong (not dictionary attackable) is preferable as it protects against password cracking proactively. Resetting a user's password after a hack is simply not as good as having a strong password that can't be cracked.

      You've basically have been twisting my words into something I never stated or implied and then have applied them to scenarios outside of what I originally responded to. At this point I'm simply just going to ignore you.

      You trolling or what?

    15. Re: There we go again by jxander · · Score: 2

      The kicker (for me) is that many websites DON'T allow certain character sets.

      I've had websites tell me that I'm not allowed to use special characters. One of which was a financial institution.

      --
      This signature is false.
    16. Re: There we go again by tlhIngan · · Score: 2

      Only if you're dumb enough to let authentication program be suspceptible to such an attack. Dictionary attacks can be trivially defeated by rating limiting tries and after, say, 5 tries not allowing any more attempts for some cooldown period. No attacker is going to bother if they can only have 5 tries every 15 to 20 minutes.

      Few attacks actually try to login repeatedly.

      If they do, there are botnets that help you try lots in a short period of time.

      Most attacks involve dumping the password hash database.

      And even brute forcing is getting easier. If you need a SPECIFIC password, it's not any easier, but if you have a bunch of hashes and you want a good chunk of accounts (without caring if you have every account), it's actually easy. In fact, Ars Technica covers a domain-specific brute forcer.that relies on terminology from the sites cracked to get a list of potential passwords EXTREMELY quickly. Follow this with trivial modifications to get more. If you have a list of a million passwords, you could easily derive half of them this way, and then move on to the next list.

      Remember, let's differentiate between cracking one SPECIFIC account and password, with cracking AN account and password from a list. You might be cool and use a super complex password that involves every typeable character on the keyboard, and yes, people may not find your password easy to crack. But perhaps your neighbour just used "password". Well, of the two, it's easy to crack AN account, but not a SPECIFIC account.

    17. Re:There we go again by gmhowell · · Score: 2

      Why do they want to kill my password? What's wrong with "@13 unicorn #DARPA gangbang!"? It's secure isn't it?

      Damnit, time to change the combination on my luggage again...

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    18. Re:There we go again by ArcadeMan · · Score: 2

      There's no need to nuke the website from orbit. The server is running IIS, it will implode on itself sooner or later.

    19. Re: There we go again by Culture20 · · Score: 2

      Sort of like how a destroyer is easier to lift with one's bare hands than the Empire State Building?
      The real bad part about a grammatically correct sentence is memory mutation.
      "I'm going to take my dog, Spot, to the park."
      "I'm going to take my dog to the park today."
      "I'm taking my dog, Spot, to the park today."
      "#&@*!!! What was that passphrase?"

    20. Re: There we go again by AK+Marc · · Score: 2

      If the attacker is performing the attack "offline" then you've already lost the security battle. That's the point. If you lose your password database, assume the passwords are all broken, no matter whether you have "must have 3.2 uppercase and 4.35 lowercase letters, 0.6 special characters and as many numbers as you like, so long as it doesn't start or end with a number" rules or let them use plain English sentences. A hashed " " is as meaningful as a hashed "a" so "cat dog run fast" is better than a very random 8-char password. http://xkcd.com/936/ Even if you know it's susceptible to a dictionary attack, it'll be better than most.

      But the point is, once they have your hash, you've already screwed up your security. Especially if you don't then change all the passwords.

    21. Re: There we go again by AK+Marc · · Score: 3

      Yup. Because SQL injection attacks work in passwords, especially when you have a 4,000 old COBOL system.

    22. Re: There we go again by AK+Marc · · Score: 3, Interesting

      Sometimes it seems like the sites make their password rules match banks. Then, if you can't find anything else that works, use your bank password. The site then has your email, name and bank password. They can try that combo on all the major bank sites, and could get access.

      I'm surprised more black-hats don't set up "free" services with that intention.

  2. All good until someone simulates biometrics... by Anonymous Coward · · Score: 5, Insightful

    You can change a password, you can't change your retina print. What do you do when your account is compromised? Get new eyes?

    1. Re:All good until someone simulates biometrics... by peragrin · · Score: 3, Insightful

      New eyes , new finger prints, and new DNA.

      What happens if you get sick or injured? Can you imagine pink eye with retinal scanners? Finger print scanners are fooled by gummy bears.

      --
      i thought once I was found, but it was only a dream.
    2. Re:All good until someone simulates biometrics... by rodrigoandrade · · Score: 2

      Pink eyes, eh? Don't go to work stoned, then..

    3. Re:All good until someone simulates biometrics... by Thanshin · · Score: 5, Funny

      Finger print scanners are fooled by gummy bears.

      Where I work, the scanners are quite high. Way beyond the reach of even the tallest gummy bears.

    4. Re:All good until someone simulates biometrics... by Anonymous Coward · · Score: 4, Funny

      They may be short, but don't be fooled - they can actually reach quite high if they have their juice with them.

    5. Re:All good until someone simulates biometrics... by mellon · · Score: 4, Insightful

      Exactly right. Biometric passwords are much easier to fake, because you can't change them. They also provide a nice means of identifying surveillance targets. It's almost as if these guys are getting direction from the NSA or something.

    6. Re:All good until someone simulates biometrics... by Anonymous Coward · · Score: 3, Funny

      For those of you that don't get the joke: there was a cartoon about bouncing gummi bears in the 80s. It has an amazing theme song:
      https://www.youtube.com/watch?...

    7. Re:All good until someone simulates biometrics... by Bob9113 · · Score: 3, Funny

      >> Finger print scanners are fooled by gummy bears.

      > Where I work, the scanners are quite high.

      Aww, come on, now, no need to point fingers. If you had to sit there and check people's fingerprints all day you might spark up a bowl and get tempted by gummi bears once in a while too.

    8. Re:All good until someone simulates biometrics... by donaldm · · Score: 2

      You can change a password, you can't change your retina print. What do you do when your account is compromised? Get new eyes?

      Instead of all this BS, just make an app that stores all the sub-passwords from a master password.

      There are plenty of apps that allow you to store your passwords in a database. Do a lookup on "password manager" and you should get over 250,000,000 hits. The problem is that you need to make sure that the passwords you use are not trivial and should be preferably over 8 alpha-numeric characters in length as well as having at least one special character (ie. !,@$# ... etc). A password generator is actually very good for this however the more complex a password the more you need to rely on a password database or at least the sites you are connecting to being able to save your password such as in your browser.

      The biggest problem I have faced is the arbitrary password rules. Some sites require you have to choose from .\$[] character set whereas others cannot have it in the password. Some have length limits and some minimums. Some require at least two alphanumeric characters. Some allow phrases some don't.

      That is not really a problem if you generate appropriate passwords and have a password manager.

      Of course at some stage you really must remember at least one or two passwords. One to log you into your PC, Workstation, Mainframe etc and the other to access your password database if you have one. Oh yes you also have to have a contingency plan in case you are compromised such as knowing who to contact and it does not hurt knowing how to restore your data as well, assuming you do backups.

      --
      There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
    9. Re:All good until someone simulates biometrics... by BenJeremy · · Score: 2

      I had a cancerous tumor on my retina.

      After treatment, which included radiation (Chip sewn on the lower back part of my eyeball for a week) and lasers, along with the ongoing process of the optic nerve dying from the radiation exposure, I suspect my retina is quite different, and still changing, from 4 years ago when the tumor was treated.

      Retinal patterns DO change some times. It's rare, but it happens.

    10. Re:All good until someone simulates biometrics... by mrxak · · Score: 2

      With physical keys, a lot of people forget about securing their keys. They leave them out where they can be photographed, for example, or quickly imprinted, or even just compared to another key with all the bite codes on it so the numbers can be noted.

      Same goes for locks. A lot of people don't secure their locks, either, which leaves an attacker plenty of opportunity to bypass. Even an area with security which will detect an attempt to pick a lock or force it open, is still vulnerable. You see a guy go up to a door, stick a key in the lock like he belongs there, then suddenly he "forgets" something and walks away without opening the door. You might not think twice about it in a busy office building, but that guy just got pin imprints and will be back every day to do the same thing again, or send in somebody else, until one day an attacker walks up with a manufactured key that opens the lock and goes right in.

      "Something you have" like physical keys aren't that great if you don't secure them. You need to make sure that the only people who have that something are authorized to have it, and you need to restrict hardware access to the lock. It's a tricky proposition in the best of cases. Biometrics are even worse than most cases, because at least a lock on an office door can be changed if a key is lost. You can't change your biometrics. Furthermore, we're talking about digital systems here, when biometrics are inherently analog. Your analog finger, eye, or whatever is being taken in as a precise yet inaccurate digital signal, some probability function is determining if you're "close enough", and then a computer chip says you're okay. It's like having a lock where if you jiggle different keys in it, the tumbler will still turn. To put it in computer terms, it's like taking a float in as input, truncating the decimal, and using it as an integer in your finely-tuned algorithm. There's all kinds of floats out there that will get you the integer you need to make your algorithm work the way you want it to. It's no longer "something you have", it's "something that's kinda like what you have".

      "Something you know" like a combination or a password, has always been more secure. It uses math instead of the physical world and its inherent weaknesses. There's too many combinations to reasonably guess it in the amount of time you have, and you're forced to exploit some vulnerability in the locking mechanism to get in, like using a blow torch to melt the locking bolt, or exploit some vulnerability in the user of the lock, like he was stupid and used his birthdate as the combination, or wrote it down. Passwords, and combinations, are digital, instead of analog, which means there's exactly one password or combination that will work, instead of an infinite number of "close enoughs".

      You still need security with your lock and key, whether your key is something you know or something you have, but at least with digital, changeable keys, you have the power of discrete math on your side, and if you do lose lock or key security, you can go ahead and change your key.

      And if I've piqued anyone's interest in security of physical locks and physical keys, I highly recommend the books by pen-tester Deviant Ollam, specifically Keys to the Kingdom which covers a number of attacks most people never consider when they're securing their offices, server rooms, etc. Practical Lock Picking is good too, if you want to learn how locks are defeated by, surprise, picking them (bumping, shimming, and bypassing too).

  3. Ultimately... by Anonymous Coward · · Score: 5, Insightful

    Ultimately whatever password replacement you come up with gets turned into TCPIP packets over the intertubes. Whether you are measuring my height, fingerprint, penis size or whatever metric you come up with, it gets turned into 0's and 1's that I can grab and duplicate. It is still information on a remote server than can be hacked and used by third parties.

    And worse... once hacked, I can't do much to change my biometrics... so I'm totally screwed once the host server is hacked and a million biometric accounts are compromised.

    1. Re:Ultimately... by digitig · · Score: 5, Funny

      Whether you are measuring my height, fingerprint, penis size or whatever metric you come up with

      Penis size is pretty useless as a biometric. It changes depending on the site being accessed.

      --
      Quidnam Latine loqui modo coepi?
    2. Re:Ultimately... by daid303 · · Score: 2

      Whether you are measuring my height, fingerprint, penis size or whatever metric you come up with

      Penis size is pretty useless as a biometric. It changes depending on the site being accessed.

      So, that's perfect, password per site, and hard to fake.

  4. presumably so... by Anonymous Coward · · Score: 5, Insightful

    ...when the NSA wants to tap into various accounts, they can track exactly who they belong to and who accesses them because it will be linked to your personally identifiable biometrics

  5. I can't change my fingerprint by Ubi_NL · · Score: 5, Insightful

    I can change my password anytime if I think somebody copied it. I cannot change my fingerprint or retina. There is no way I'm giving random webshops or google my biometric data.

    --

    If an experiment works, something has gone wrong.
    1. Re:I can't change my fingerprint by Another,+completely · · Score: 2

      It's more likely that your biometric would just unlock a stick that you carry around with you. The stick would then use an internally-generated key to authenticate you to the remote site.

    2. Re:I can't change my fingerprint by bombman · · Score: 2

      Can I have a glass of formaldehyde and eyeballs next to my computer i can use if i want to change my password?

  6. As long as certain rules are kept by Thanshin · · Score: 5, Interesting

    I'm ready to switch passwords for anything else as long as:
    1 - It can't be extracted from me by an easier method than torture or blackmail.
    2 - It stops working forever if I'm dead.

    Otherwise, some blood will have to wash away the naivete. Again.

    1. Re:As long as certain rules are kept by LWATCDR · · Score: 3, Insightful

      "2 - It stops working forever if I'm dead."
      That is what I am worried about. I would like my wife to have access to my online accounts if for no other reason than to say good bye for me.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    2. Re:As long as certain rules are kept by judoguy · · Score: 3, Insightful
      Good point. I'm at an age where my friends are dying every year or so. As someone who has had to "close up shop" for some of them, it's a royal bitch to do when their online life can't be accessed. Stopping the mail, shutting down the online business, etc.

      "Oh, they should have prepared for that in advance, as soon as they knew they were going to die". Yeah, well, perhaps in some fantasy world. No, the survivors clean up in real life.

      --
      Peace is easy to achieve, just surrender. Liberty is much harder get/keep.
  7. Re:Passwords died in the 80s by szmccauley · · Score: 2

    In the 80s we didn't even bother with passwords, okay maybe by the late 80s. And every machine on the network had an IP that was directly on teh internets. As for this article, it's yet another example of how stupid people, even the intelligent, are when it comes to passwords. Who the fsck writes down a dizzying array of passwords? I know about 5 passwords off by heart at any given time, and use a password manager and an encrypted database to hold all of my passwords. Of course, without 2-factor auth those lists of passwords are seriously dangerous and that, dear humans, is where the danger lies. If anyone manages to crack my passowrd manager or my encrypted database, I'm fscked. Okay, let's hear what the folks have to say about this age old problem.

  8. Passwords don't need to be killed by nine-times · · Score: 4, Insightful

    Passwords don't need to be killed. If you're thinking about replacing it with biometrics, I think that's thinking about the problem the wrong way too. The fact is, we already have all the technology we need to solve this problem much better than we do today. It's simple: instead of passwords, you should have a password protected private key, with a single password, and then use public keys for authentication. That way, you only need to know one password, and you've also eliminated a lot of the danger of snooping on connections because the private key isn't being sent.

    Of course, it would require that everyone pretty much agree on one set of standards for how it's supposed to be implemented, and than developers have to build their products with those standards. Then you probably also want some trustworthy and inexpensive/free Certificate Authorities. Ideally you'd want to be able, though not required, to use the same private key for everything-- email encryption, ssh logins, maybe even credit card purchases-- so you'd need mechanisms for managing your keys, keeping them safe but also making them available when needed. Throw in some dual-factor authentication where you want a high level of security, and you've basically solved the issue.

    1. Re:Passwords don't need to be killed by ZorroXXX · · Score: 2
      Actually, a solution very similar to what you describe are currently beeing developed as SQRL - Secure Quick Reliable Login. The main highlights and uniqeness of this is:
      • There is no trusted third party. There is the only a) the user and b) the website (and also notice that each website will receive different identities, so no cross site spying).
      • The creator, Steve Gibson, is doing this just because it is a good security solution and have no other interests. He has a long track record of being an security expert, starting the podcast Security Now! in 2005, currently up to 467 episodes.
      --
      When you are sure of something, you probably are wrong (search for "Unskilled and Unaware of It").
  9. Won't work by DaMattster · · Score: 2

    You can kill the password in favor of strong security tokens but if the underlying code is poorly written and full of security holes, then it won't be any more secure than what we have now. If you can steal a few retinal images through an exploit, you could, in theory, make a model with the retinal pattern.

  10. PKI SSL by Sobrique · · Score: 2
    We're used to using SSL from client to server. But it works both ways around. You can use client side SSL certificates to authenticate. Client side SSL certificates that you can lock down with a decent passphrase, SSLVerifyClient

    Not as hard to implement as some of the pipe dreams out there. Of course, it does require a degree of tech savvy on the part of users - and more importantly, enforcing it's use, to avoid laziness bypassing.

    Then your challenge becomes certificate transport - you'll need a way to carry around your cert, or somehow get hold of it when you need it, which is easier said than done. The real advantage of passwords is their portability. Biometrics have a similar advantage, but as already noted - are a bit harder to revoke/change.

  11. So...revoke the certificate by Overzeetop · · Score: 4, Informative

    Any biometric password should be based on a certificate, not a direct digital representation of the biometric.

    --
    Is it just my observation, or are there way too many stupid people in the world?
    1. Re:So...revoke the certificate by Graydyn+Young · · Score: 2
      This is correct. Take a look at what these guys are doing with biometrics:

      getnymi.com

      They aren't sending your biometric data all over the internet. They verify your identity on device and then send a token around.

    2. Re:So...revoke the certificate by Overzeetop · · Score: 2

      As a professional engineer, I have to certify the designs I send out were created by me. In the past, a rubber stamp and an ink signature were used (still are in many places), but I sign everything digitally. I've created and posted a public key hosted on my web server which has been sufficient for 99.9% of clients to date - all but 2. One client required a know authority to hold the certificate, but wasn't willing to pay for it, so we "compromised" and I hand signed the sheets. The other client simply wouldn't accept digital signatures.

      --
      Is it just my observation, or are there way too many stupid people in the world?
  12. 666 by musmax · · Score: 2, Interesting

    And he causes all, the small and the great, and the rich and the poor, and the free men and the slaves, to be given a mark on their right hand or on their forehead, and he provides that no one will be able to buy or to sell, except the one who has the mark, either the name of the beast or the number of his name. Rev 13:17

  13. The problem is false negative by Geoffrey.landis · · Score: 3, Insightful

    What happens if you get sick or injured? Can you imagine pink eye with retinal scanners?

    Yes, this is the serious problem-- just as serious as the problem of people fooling the password-alternative is the problem of the false negatives: getting locked out.

    Notice that most of these weren't fingerprint scanners or retinal scanners-- they were stuff like gait monitors, or even more bizarre stuff, like listening to your heartbeat. So, if you twist your ankle--or even buy a new pair of shoes-- you're out of luck. Taking pseudoephedrine for a cold? Ooops, your heartrate is different. You're locked out.

    --instead of using these instead of password, however, what about if you use alternate ID as a second check. It doesn't lock you out, but it does trigger a watchdog alert that pays attention to what you're doing.

    You can change a password, you can't change your retina print. What do you do when your account is compromised? Get new eyes?

    Yes, we've all seen dozens of those science fiction stories where they steal people's eyes, or cut off their fingers, or take swabs of their DNA.

    --
    http://www.geoffreylandis.com
    1. Re:The problem is false negative by geekoid · · Score: 5, Insightful

      "Yes, we've all seen dozens of those science fiction stories where they steal people's eyes, or cut off their fingers, or take swabs of their DNA."
      cute, but not what the poster is talking about.

      Your info, weather its a password, or the bio-metric info will get turned into a string and stored in a database.
      Once that database in compromised, your bio-metric info on EVERY system you log into needs to be change to a different bio metric. They don't actually need to physical eye.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  14. They should watch "Archer"... by QilessQi · · Score: 5, Funny

    Pam: Oh, OK, then good luck with all the biometric scanners. Unless you wanna cut off my fingers and scoop out my retinas.

    Kidnappers look at each other.

    Pam: Oh, don't be dicks!

  15. A standardized interface for changing passwords by Marrow · · Score: 5, Insightful

    Every single site has a different way of giving you a way to change your password. This makes it impossible to write programs to write programs to change your password....like a password manager for instance. Imagine if you could just type in your new password into your password manager program, and it changes all the passwords it manages with one click. They could all be randomly generated and different for every site. Hints, recovery, email addresses, could all be updated with one click. With a history as to the previous versions in case something went south.

    Instead of struggling with writing all the captcha's, and strength meters, and interfaces, and all the CRAP that the every site on the planet does differently. Just standardize the interface and maintenance of passwords. And then standardize the strength of the generator programs. And voila, permanent security that is controlled where it should be: in your hands.

  16. Half of this is good news by houghi · · Score: 2

    The good part is that they are concerned about passwords. The bad news is that they do not come up with a good alternative.

    There are two issues with passwords. The first is that we are looking for a technical problem with what is essentialy a social problem. Security in itself is already a social problem. How many people will give uup their password to the IT guy or their boss without any question? To their SO, kids or parents?

    The second isssue is that we have way too many passwords to remember and there is no single solution. (1) IT people are only looking to how THEIR system is secured and look at it from an, again, technical and not a social point of view. They do not count in the weakest point : humans.

    And as long as you do not caqlcualte those in, it won't be solved.
    So instead of saying 'We want to replace it with ..." they should have said "We want to replace it". That way you are open for a REAL solution.

    (1) If you have a solution, please let me know. It must be one that I can use at home (Linux), at work (Windows, but I am not allowed to install anything and have no Internet access and am not allowed to use any cellphone or other device), on my phone, on PCs that are not mine, on my ATM machine.

    --
    Don't fight for your country, if your country does not fight for you.