SHA password hashes

From ArchWiki
Revision as of 01:38, 4 May 2011 by Filam (talk | contribs) (Why Should You Use SHA-2?)
Jump to: navigation, search

Why Should You Use SHA-2?

In Linux distributions login passwords are commonly hashed and stored in the /etc/shadow file using the MD5 algorithm. The security of the MD5 hash function has been severely compromised by collision vulnerabilities. This does not mean MD5 is insecure for password hashing but in the interest of decreasing vulnerabilities a more secure and robust algorithm that has no known weaknesses (i.e. SHA) is recommended.

The following tutorial uses the sha512 hash function, which has been recommended by the NSA for Red Hat Enterprise Linux 5. Alternatively, SHA-2 consists of three additional hash functions with digests that are 224, 256 or 384 bits.

Warning: The very minimal terminal manager fgetty doesn't support sha512 password hashing. Enabling sha512 with fgetty will cause you to be locked out. The default tty manager agetty and minimal tty manager mingetty both support sha512.

Editing the Necessary Files

Note: You must have root privileges to edit the files within this section.

Editing /etc/pam.d/passwd

A default Template:Filename should look like the following:

#password	required difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
#password	required md5 shadow use_authtok
password	required md5 shadow nullok

Open Template:Filename with a text editor and replace md5 with sha512 on the uncommented line.

Note: For a more detailed explanation of the Template:Filename password options check the pam man page.

The rounds=N parameter is for Key Strengthening the choice of N has a more important impact on Security than the hashfunction in use! N = 65536 means that the Attacker has to compute 65536 hashes for each password he tests against the hash in your /etc/shadow, so he is slown down by that factor. Also this means that your box has to do 65536 hashes everytime you log in ... but even on slow computers that takes less than 1 second.

After doing so, the file should look like this:

#password	required difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
#password	required md5 shadow use_authtok
password	required sha512 shadow nullok rounds=65536

Editing /etc/default/passwd

Your Template:Filename file most likely looks like this:

# This file contains some information for
# the passwd (1) command and other tools 
# creating or modifying passwords.

# Define default crypt hash
# CRYPT={des,md5,blowfish}

# Use another crypt hash for group passwowrds.
# This is used by gpasswd, fallback is the CRYPT entry.

# We can override the default for a special service
# by appending the service name (FILES, YP, NISPLUS, LDAP)

# for local files, use a more secure hash. We
# don't need to be portable here:
# sometimes we need to specify special options for
# a hash (variable is prepended by the name of the
# crypt hash).

# For NIS, we should always use DES:

Once again, the change is very simple. Change




or whatever SHA-2 encryption you are using.

Note: It's unclear whether this is still necessary with the Template:Filename mechanism.

Editing /etc/login.defs

According to passwd's man page, this file has to be edited when the Template:Filename mechanism is used for storing passwords. Add the following line (adjusted to whatever algorithm you use) to Template:Filename:


Final Steps

Even though you have changed the encryption, your passwords are not automatically rehashed!

To fix this, you must reset all user passwords so that they can be rehashed.

As root, the command

# passwd <username>

where <username> is the name of the user whose password you are changing, will allow you to do this. Simply re-enter their current password, and it will be rehashed to the more secure SHA-2 version!

To verify that your passwords have been rehashed, check the Template:Filename file as root. Passwords hashed with sha256 should begin with a $5 (passwords hashed with sha512 will begin with $6).