Difference between revisions of "SHA password hashes"

From ArchWiki
Jump to: navigation, search
(updated and added templates; replaced AUR link with Template:AUR; fixed capitalization of the hash function names)
(use https for links to archlinux.org)
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Security (English)]]
+
[[Category:Security]]
{{out of date}}
+
{{note|1= With {{pkg|shadow}} 4.1.4.3-3 ''sha512'' is the default for new passwords (see [https://bugs.archlinux.org/task/13591#comment85993 bug 13591] and corresponding [https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/shadow&id=98001501a8306ef5a0df55d1cffc048851894940 commit]).}}
{{note|1= With {{pkg|shadow}} 4.1.4.3-3 ''sha512'' is the default for new passwords (see [https://bugs.archlinux.org/task/13591#comment85993 bug 13591] and corresponding [http://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/shadow&id=98001501a8306ef5a0df55d1cffc048851894940 commit]).}}
+
 
 +
If your current password was created with {{pkg|shadow}} version prior to 4.1.4.3-3 (2011-11-26) you are using MD5. To start using a SHA-512 hash you just need to change your password with ''passwd''.
  
 
==Benefits of SHA-2 over MD5==
 
==Benefits of SHA-2 over MD5==
 
In Linux distributions login passwords are commonly hashed and stored in the {{ic|/etc/shadow}} file using the [[Wikipedia:MD5|MD5 algorithm]]. The security of the MD5 hash function has been severely compromised by [[Wikipedia:MD5#Collision_vulnerabilities|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 (e.g. SHA-512) is recommended.
 
In Linux distributions login passwords are commonly hashed and stored in the {{ic|/etc/shadow}} file using the [[Wikipedia:MD5|MD5 algorithm]]. The security of the MD5 hash function has been severely compromised by [[Wikipedia:MD5#Collision_vulnerabilities|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 (e.g. SHA-512) is recommended.
  
The following tutorial uses the ''sha512'' hash function, which has been recommended by the NSA for Red Hat Enterprise Linux 5. Alternatively, [[Wikipedia:SHA-2|SHA-2]] consists of three additional hash functions with digests that are 224, 256 or 384 bits.
+
The following tutorial uses the SHA-512 hash function, which has been recommended by the United States' National Security Agency (NSA) for Red Hat Enterprise Linux 5. Alternatively, [[Wikipedia:SHA-2|SHA-2]] consists of four additional hash functions with digests that are 224, 256, 384, and 512 bits.
  
===Support===
+
==Increasing Security==
{{Warning|The very minimal terminal manager ''fgetty'' does not support SHA-512 password hashing by default. Enabling SHA-512 with the default ''fgetty'' will cause you to be locked out.}}
+
{{note|You must have root privileges to edit this file.}}
Arch Linux's default tty manager  ''agetty'' and the minimal tty manager ''mingetty'' both support SHA-512. Additionally, a patched version of ''fgetty'' is in the [[Arch User Repository|AUR]] named {{AUR|fgetty-pam}} which adds SHA-512 support.
+
The {{ic|1=rounds=N}} option helps to improve [[Wikipedia:Key stretching|key strengthening]]. The number of rounds has a larger impact on security than the selection of a hash function. For example, {{ic|1=rounds=65536}} means that an attacker has to compute 65536 hashes for each password he tests against the hash in your {{ic|/etc/shadow}}. Therefore the attacker will be delayed by a factor of 65536. This also means that your computer must compute 65536 hashes every time you log in, but even on slow computers that takes less than 1 second. If you do not use the {{ic|rounds}} option, then glibc will '''default''' to '''5000''' rounds for SHA-512. Additionally, the default value for the {{ic|rounds}} option can be found in {{ic|sha512-crypt.c}}.
  
==Editing the Necessary Files==
+
Open {{ic|/etc/pam.d/passwd}} with a text editor and add the {{ic|rounds}} option at the end of of the uncommented line. After applying this change the line should look like this:
{{note|You must have root privileges to edit the files within this section.}}
+
password required pam_unix.so sha512 shadow nullok '''rounds=65536'''
===Editing /etc/pam.d/passwd===
+
A default {{ic|/etc/pam.d/passwd}} should look like the following:
+
#%PAM-1.0
+
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
+
#password required pam_unix.so md5 shadow use_authtok
+
password required pam_unix.so md5 shadow nullok
+
 
+
Open {{ic|/etc/pam.d/passwd}} with a text editor and replace {{ic|md5}} with {{ic|sha512}} on the uncommented line. At the end of of the uncommented line, add the {{ic|rounds}} option.
+
 
+
The {{ic|1=rounds=N}} option helps to improve [[Wikipedia:Key Strengthening|key strengthening]]. The number of rounds has a larger impact on security than the selection of a hash function. For example, {{ic|1=rounds=65536}} means that an attacker has to compute 65536 hashes for each password he tests against the hash in your {{ic|/etc/shadow}}. Therefore the attacker will be delayed by a factor of 65536. This also means that your computer must compute 65536 hashes every time you log in, but even on slow computers that takes less than 1 second. If you do not use the {{ic|rounds}} option, then glibc will default to 5000 rounds for SHA-512. Additionally, the default value for the {{ic|rounds}} option can be found in {{ic|sha512-crypt.c}}.
+
  
 
{{note|For a more detailed explanation of the {{ic|/etc/pam.d/passwd}} password options check the [http://linux.die.net/man/8/pam_unix PAM man page].}}
 
{{note|For a more detailed explanation of the {{ic|/etc/pam.d/passwd}} password options check the [http://linux.die.net/man/8/pam_unix PAM man page].}}
  
After applying the above changes your {{ic|/etc/pam.d/passwd}} file should look like this:
+
==Re-Hash the Passwords==
#%PAM-1.0
+
Even though you have changed the encryption settings, your passwords are not automatically re-hashed. To fix this, you must reset all user passwords so that they can be re-hashed.
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
+
#password required pam_unix.so md5 shadow use_authtok
+
password required pam_unix.so '''sha512''' shadow nullok '''rounds=65536'''
+
 
+
===Editing /etc/default/passwd===
+
Your default {{ic|/etc/default/passwd}} file should look 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}
+
CRYPT=des
+
+
# Use another crypt hash for group passwowrds.
+
# This is used by gpasswd, fallback is the CRYPT entry.
+
# GROUP_CRYPT=des
+
+
+
# 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
+
# do not need to be portable here:
+
CRYPT_FILES=blowfish
+
# sometimes we need to specify special options for
+
# a hash (variable is prepended by the name of the
+
# crypt hash).
+
BLOWFISH_CRYPT_FILES=5
+
+
# For NIS, we should always use DES:
+
CRYPT_YP=des
+
On line 7 of the above example file, change
+
CRYPT=des
+
to
+
CRYPT=sha512
+
 
+
{{Note|It is unclear whether this is still necessary with the {{ic|/etc/shadow}} mechanism.}}
+
 
+
{{Note|It is not necessary to edit {{ic|/etc/login.defs}}. For more see [https://bugs.archlinux.org/task/13591#comment85993 here].}}
+
 
+
==Final Steps==
+
Even though you have changed the encryption, your passwords are not automatically re-hashed. To fix this, you must reset all user passwords so that they can be re-hashed.
+
  
 
As root issue the following the command,
 
As root issue the following the command,
Line 78: Line 26:
  
 
To verify that your passwords have been re-hashed, check the {{ic|/etc/shadow}} file as root. Passwords hashed with SHA-256 should begin with a {{ic|$5}} and passwords hashed with SHA-512 will begin with {{ic|$6}}.
 
To verify that your passwords have been re-hashed, check the {{ic|/etc/shadow}} file as root. Passwords hashed with SHA-256 should begin with a {{ic|$5}} and passwords hashed with SHA-512 will begin with {{ic|$6}}.
 +
 +
==Known Problems==
 +
===fgetty===
 +
Arch Linux is using SHA-512 password hashing by default (since 2011-11-26). The very minimal terminal manager ''fgetty'' does not support SHA-512 password hashing by default. Enabling SHA-512 with the default ''fgetty'' will cause you to be locked out.
 +
A patched version of ''fgetty'' is in the [[Arch User Repository|AUR]] named {{AUR|fgetty-pam}} which adds SHA-512 support.

Revision as of 00:34, 6 December 2012

Note: With shadow 4.1.4.3-3 sha512 is the default for new passwords (see bug 13591 and corresponding commit).

If your current password was created with shadow version prior to 4.1.4.3-3 (2011-11-26) you are using MD5. To start using a SHA-512 hash you just need to change your password with passwd.

Benefits of SHA-2 over MD5

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 (e.g. SHA-512) is recommended.

The following tutorial uses the SHA-512 hash function, which has been recommended by the United States' National Security Agency (NSA) for Red Hat Enterprise Linux 5. Alternatively, SHA-2 consists of four additional hash functions with digests that are 224, 256, 384, and 512 bits.

Increasing Security

Note: You must have root privileges to edit this file.

The rounds=N option helps to improve key strengthening. The number of rounds has a larger impact on security than the selection of a hash function. For example, rounds=65536 means that an attacker has to compute 65536 hashes for each password he tests against the hash in your /etc/shadow. Therefore the attacker will be delayed by a factor of 65536. This also means that your computer must compute 65536 hashes every time you log in, but even on slow computers that takes less than 1 second. If you do not use the rounds option, then glibc will default to 5000 rounds for SHA-512. Additionally, the default value for the rounds option can be found in sha512-crypt.c.

Open /etc/pam.d/passwd with a text editor and add the rounds option at the end of of the uncommented line. After applying this change the line should look like this:

password	required	pam_unix.so sha512 shadow nullok rounds=65536
Note: For a more detailed explanation of the /etc/pam.d/passwd password options check the PAM man page.

Re-Hash the Passwords

Even though you have changed the encryption settings, your passwords are not automatically re-hashed. To fix this, you must reset all user passwords so that they can be re-hashed.

As root issue the following the command,

# passwd <username>

where <username> is the name of the user whose password you are changing. Then re-enter their current password, and it will be re-hashed using the SHA-2 function.

To verify that your passwords have been re-hashed, check the /etc/shadow file as root. Passwords hashed with SHA-256 should begin with a $5 and passwords hashed with SHA-512 will begin with $6.

Known Problems

fgetty

Arch Linux is using SHA-512 password hashing by default (since 2011-11-26). The very minimal terminal manager fgetty does not support SHA-512 password hashing by default. Enabling SHA-512 with the default fgetty will cause you to be locked out. A patched version of fgetty is in the AUR named fgetty-pamAUR which adds SHA-512 support.