Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Re^2: Adjust bcrypt cost to prevent future password hash attacks

by andreas1234567 (Vicar)
on Jun 12, 2012 at 08:24 UTC ( #975710=note: print w/ replies, xml ) Need Help??


in reply to Re: Adjust bcrypt cost to prevent future password hash attacks
in thread Adjust bcrypt cost to prevent future password hash attacks

Data must be secured in transit and at rest. TLS protects data in transit only, and does not prevent offline attacks (e.g. recent Linkin breach).

We need both TLS and bcrypt, not just the former.

--
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]


Comment on Re^2: Adjust bcrypt cost to prevent future password hash attacks
Re^3: Adjust bcrypt cost to prevent future password hash attacks
by Anonymous Monk on Jun 12, 2012 at 08:52 UTC

    and does not prevent offline attacks

    of course not :) I wasn't suggesting switching away from bcrypt, merely that the cost is not as important for online attacks, those can be throttled effectively

    but, for offline, you should use encrypted harddisks and not rely on bcrypt alone

      You seem to be associating "offline attacks" with physical theft of the hardware. However, they much more often (including in the recent LinkedIn/eHarmony cases) involve cases where an attacker has duplicated the contents of the user database. In such cases, encrypting the hard drive is completely irrelevant.

      Each of these measures is only applicable to certain types of attack:

      • TLS only matters if someone is attempting to access data in transit.
      • Disk encryption only matters if the hardware running the system is physically stolen.
      • The hashing method only matters if the attacker has direct access to (a copy of) the password database.
      Whatever you may be trying to secure, you need to assess which threats are actually relevant to you and implement the appropriate security measures based on that (and on the value of the system/its data).
      I beg to differ. Ideally, it should be safe to publish the hashes online as no-one should be able to search the password space in reasonable time.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://975710]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (5)
As of 2014-08-30 21:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The best computer themed movie is:











    Results (294 votes), past polls