Language Selection

English French German Italian Portuguese Spanish

Voluntary Disclosure Is the Threat to Password Security

Filed under
Security

Computers can remember complex bits of data effortlessly, but people routinely fumble that task. Naturally, one of the big trends in computing security is making users memorize complex passwords -- then regularly wipe those from their memory in favor of equally obscure replacements.

To judge from the stern advice handed out by banks, Internet providers and information technology departments -- often, I suspect, after prodding by accounting departments and liability lawyers who don't want to be blamed for a security breach -- computer security hinges almost entirely on you choosing a string of letters, numbers and symbols in an order that has no correlation to any word or phrase that has ever been spoken or written in English or any other language.

That's fiction. First, while avoiding obvious passwords still constitutes a common-sense defense, that won't stop most password theft attempts these days. Second, forcing people to choose the most obscure passwords possible, then choose new ones every few months, is more likely to grease the skids for a successful compromise of those users' accounts.

This is because passwords aren't stolen in ways you might expect; a bad guy doesn't sit down in front of your computer and start typing in guess after guess until he succeeds. In the real world, accounts are usually cracked in two ways -- only one of which can be slowed or stopped by the use of a sufficiently inscrutable password.

One is to get access to the computer that stores users' login info. If the master password file stored on that machine is encrypted -- it should be, but sometimes is not -- the attacker then runs a password-cracking program to break that encoding. Otherwise, he or she can read the file as-is.

The other method relies on someone surrendering a password voluntarily. For example, an attacker can hide a program on a victim's computer to record each tap of the keyboard -- often by exploiting an old, long-since-patched vulnerability in Windows or by hiding the "keystroke logger" in a tempting download.

Or the attacker can just ask nicely for the password -- what's called "social engineering." The victims can be technical staff at a bank or an Internet provider who get a call from somebody claiming to be a colleague elsewhere in the company. Or the victims can be individual users who receive "phishing" e-mails imploring them to verify their account information by clicking on a link to a phony Web site done up to appear like that of a trusted institution.

The quality of a password matters only against the first type of attack -- the brute-force, code-breaking assault, which will hit pay dirt more quickly if stored passwords appear in dictionaries.

That's why security experts tell password creators to avoid using real words or names, even when altered by substituting letters with similar-looking numbers or symbols (for example, replacing "i" with "!" or "1"). One common suggestion is to use words only as ingredients -- say, by combining the first letters of names of friends or titles of favorite books.
But if an attacker employs keystroke logging or social engineering, it doesn't matter whether your password is "password" or "92nkkcx-j1!" Even the most inscrutable login offers no defense against those tactics -- which are what most attackers seem to employ these days.

"If you go back 10 years ago, password cracking was the way to do things," said Marty Lindner, a senior member of the technical staff at the CERT Coordination Center, the network-security center founded at Carnegie Mellon University in 1988. Now, however, he said that phishing and other social engineering attacks are "far more prevalent, far more devastating than anything else."

Granted, getting actual numbers on how people's accounts were broken into is difficult -- few institutions want to discuss how some teenage hacker managed to own them. But there's no arguing that phishing and spyware attacks are only getting worse, and understandably so; why should an Internet con artist waste time mastering password-cracking routines when there are smoother roads into the bank vault?

And yet too many companies seem content to rely on password Puritanism as their response. Sometimes it's just silly -- for example, when some newspaper sites force readers to choose passwords with at least one number.

But more often, it's self-defeating. When users are pushed to remember too-obscure passwords, they'll start writing them down on Post-It notes stuck to a monitor or (worse yet) start reusing passwords among multiple high-value accounts. Worst of all is the policy of some companies and financial institutions to require users to change passwords every 30 or 90 days.

Not only do those periods still offer more than enough time for a minimally competent hacker to swipe an account login, the regular changing of passwords can easily soften up people for social engineering attacks.

Think of what happens every time a user must change a password -- or inevitably forgets the login of the month or the quarter: They'll have to go to a Web page or call up a help desk to get the password reset. That interaction represents a regularly scheduled opportunity for an attacker to try to step in and impersonate either party.

A few weeks ago, confronted by an obscure Web-mail login subject to one of these inane password-expiration rules, I called the support number listed on that site to have my password reset. (No, I won't name the firm involved). I expected to have the new login e-mailed to me -- but instead the helpful fellow on the other end of the line just read it to me over the phone, making no attempt to verify my identity.

If I'd been interested in stealing access to somebody else's account, I could have had a lot of fun. Instead, I could only wonder why we keep wasting our time with these illusory measures.
There are real problems with network security these days. But treating customers as if they were reprogrammable robots won't solve any of them.

By Rob Pegoraro.

More in Tux Machines

Red Hat News

  • Red Hat's Results Underscore its Growing Focus on OpenStack
    Late last week, Red Hat reported earnings per share of 55 cents on revenue of $600 million, beating estimates of 54 cents and $590 million, respectively. One thing that went unsaid across much of the coverage is that the company is in the midst of a major shift in its strategy toward OpenStack-based cloud computing, and it looks like service revenues and positive momentum from that effort are starting to arrive. "Our growth was driven in part by expanding our footprint with customers as we closed a record number of deals over $1 million, up approximately 60 percent year-over-year," Red Hat CEO Jim Whitehurst said during his company's earnings call. Seven of the top 30 deals had OpenStack in there, nine had RHEV," Whitehurst said. "We had three OpenStack deals alone that were over $1 million. So I think we're seeing really, really, really good traction there."
  • Red Hat targets $5-b revenue in five years
    Open-source technology firm Red Hat Inc, which hit the $2-billion revenue milestone two quarters ago, is looking to achieve $2.4 billion in FY 2017 and $5 billion in the next five years. The company is betting on India, its second largest operation outside the US, as one of the key growth engines to help achieve its aspirational revenue goal of $5 billion by 2021. “India is a bright spot for Red Hat for three reasons,” Rajesh Rege, Managing Director, Red Hat India, told BusinessLine.
  • Red Hat Announces Ansible Tower App for Splunk, Enabling Intelligence and Automation Enhancements
  • Red Hat’s (RHT) “Outperform” Rating Reiterated at Raymond James Financial Inc.
  • Red Hat Inc. (RHT) PT Raised to $89.00

pump.io Servers Adoption

  • Adopt a pump.io server
    As most of you know, E14N is no longer my main job, and I've been putting my personal time, energy, and money into keeping the pump network up and running. I haven't always done a good job, and some of the nodes have just fallen off the network. I'd like to ask people in the community to start taking over the maintenance and upkeep of these servers.
  • Prodromou: Adopt a pump.io server
    There are currently around 25 servers in the federated network initially started by Prodromou, which does not count other pump.io instances. He notes that one important exception is the identi.ca site, which is significantly larger than the rest, and which he would like to find a trusted non-profit organization to maintain.

Black Lab Linux 8 Beta 3 Released

The development team is pleased to announce the new Beta release of Black Lab Linux 8 – our latest OS offering to bring the best Linux desktop distribution currently on the market. This release moves the kernel and application set away from the prior LTS 14.04 base to the new 16.04 LTS base. Black Lab Linux 8 will showcase 3 desktop environments : MATE, LXDE and GNOME 3. Other improvements include: Full EFI support Kernel 4.4.0-38 LibreOffice 5.2 GNOME Video Rhythmbox Firefox 49 Thunderbird GIMP Full multimedia codec support Read more

Intel Core i7 6800K Benchmarks On Ubuntu + Linux 4.8

While the Core i7 6800K has been available for a few months now, there hadn't been any review on it since Intel hadn't sent out any Broadwell-E samples for Linux testing this time around. However, I did end up finally buying a Core i7 6800K now that the Turbo Boost Max 3.0 support is finally coming together (at first, Intel PR said it wouldn't even be supported on Linux) so that I can run some benchmarks there plus some other interesting items on the horizon for benchmarking. Here are some benchmarks of the i7-6800K from Ubuntu 16.04 LTS with the Linux 4.8 kernel. Read more