Slashdot Mirror


Ask Slashdot: How Do You Create A Highly-Secure Password? (securitymagazine.com)

An anonymous reader writes: A security lab at Carnegie Mellon performed a study on password security recently, and issued a warning about common user misconceptions. For example, 'ieatkale88' would require 4 billion more guesses than 'iloveyou', because 'iloveyou' is one of the most common strings in passwords. And the word 'pAsswOrd' would take 4,000 times more guesses than 'p@ssw0rd', simply because "In modern day password-cracking tools, replacing letters with numbers or symbols is predictable."

But then what passwords are secure in the face of these modern password-cracking tools? As professionals in the IT industry, what advice would you give?

Leave your answers in the comments. How do you create a highly-secure password?

5 of 637 comments (clear)

  1. SHA256. by 0100010001010011 · · Score: 4, Interesting

    echo -n "<mypassword>|<username>+example.org" | sha256sum | cut -c1-20

    Need to change all my passwords? Change the cut or my password.

  2. Re:GUID by NotInHere · · Score: 3, Interesting

    Just don't get a household robot, otherwise it will turn itself on when you sleep and the hacker will guide it to your sticky collection.

  3. Poetry by Space+cowboy · · Score: 3, Interesting

    So one of the (at the time) drawbacks of my UK education was that we had to learn poems off by heart for the English Lit. exam. At the time I thought it was just about the most boring part of the curriculum, but now they're a treasure trove of password sources...

    Example (no, I don't use this one). One of the poems we had to learn was "Dulce Et Decorum Est"...


    Bent double, like old beggars under sacks,
    Knock-kneed, coughing like hags, we cursed through sludge,
    Till on the haunting flares we turned our backs
    And towards our distant rest began to trudge.
    Men marched asleep. Many had lost their boots
    But limped on, blood-shod. All went lame; all blind;
    Drunk with fatigue; deaf even to the hoots
    Of tired, outstripped Five-Nines that dropped behind.
    Gas! Gas! Quick, boys! – An ecstasy of fumbling,
    Fitting the clumsy helmets just in time;
    But someone still was yelling out and stumbling,
    And flound'ring like a man in fire or lime . . .
    Dim, through the misty panes and thick green light,
    As under a green sea, I saw him drowning.
    In all my dreams, before my helpless sight,
    He plunges at me, guttering, choking, drowning.
    If in some smothering dreams you too could pace
    Behind the wagon that we flung him in,
    And watch the white eyes writhing in his face,
    His hanging face, like a devil's sick of sin;
    If you could hear, at every jolt, the blood
    Come gargling from the froth-corrupted lungs,
    Obscene as cancer, bitter as the cud
    Of vile, incurable sores on innocent tongues,
    My friend, you would not tell with such high zest
    To children ardent for some desperate glory,
    The old Lie; Dulce et Decorum est
    Pro patria mori.

    "The old lie" being "It is a great and glorious thing to die in the service of one's country". Anyway, take the N'th character of every line - easiest is the first, until you get the number of characters you need. It's easy to remember if you know the poem, it gives you a completely unintelligible password, and it's easy to make a password hint that's opaque to pretty much everyone but you.

    Has worked for me for ages. (I'm very old, compared to you yound whippersnappers hanging around /. recently).

    Simon

    --
    Physicists get Hadrons!
  4. Re:Easy. by antdude · · Score: 1, Interesting

    What about the password for password managers? :P

    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  5. The Bigger Question by ytene · · Score: 4, Interesting

    Is there a more interesting question to ask here?

    Have we reached the point where the concept of the password itself is no longer either appropriate, or adequately secure? For example, should we be recommending use of multi-factor and/or multi-channel solutions?

    A useful question to ask is, "Where do you have to place your trust?" For example, many respondents to this thread recommend using a password manager.cOK, but how many of those people are aware of the emergence of specific threats targeting password managers, or that some solutions have been found to be insecure? How many people come to rely more and more heavily on a smartphone or similar personal device - a single object that can give access to web, email and voice authentication vectors - yet which is one of the most heavily-targeted platforms from a threat perspective?

    I am not trying to denigrate the many excellent answers given here, but I wish to point out the risk that we are taking by asking this as a closed question ("How do you create a highly-secure password?") when changing the question slightly (for example, to "What are the most pragmatic and reliable secure authentication mechanisms available?").

    As technology consumers, maybe we should be a bit more demanding about the solutions we are offered. Maybe it would be nice if we had a trustworthy and independent third party that offered a security audit rating system for commonly used service providers, like banks? This alone would drive down a lot of the risk, because to so e extent breaches can be facilitated by bad practices on the part of the service providers...

    But other options could consider available variation on the themes of something you have, something you are and something you know. Services should allow us to set our security based on a selection of two or more of that trinity, with a range of options for each... Here's a bad example... Suppose that the fingerprint reader on new Apple iDevices had an exposed API. Then suppose that a web site authentication engine integrated with this, over a secure SSL channel. You go to the site, you tap the option for fingerprint reader, then you put your pinky on the sensor.... What would it take to engineer that securely? In a combination with even the most basic of known passwords, wouldn't that be much more secure?

    Or what about something you have? How many people drive a vehicle with a remote control unlock mechanism? One German manufacturer uses a supposedly very secure rotating key mechanism that never sends the same release code twice... What if we used the same principle and allowed people to connect their car key to their keyboard via Bluetooth, using the same or similar principle to integrate an everyday object like a car key as a "something you have" factor?

    Both of these are spur-of-the-moment suggestions and likely flawed, but I just wanted to push us past the idea that the right solution is still a password. Respectfully, that's still only single-factor and thus still implicitly weak.