Difference between revisions of "SHA password hashes"

From ArchWiki
Jump to: navigation, search
m (Fixes typo in my previous edit)
(minor style fixes, see Help:Style)
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
[[Category:Security]]
 
[[Category:Security]]
{{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]).}}
+
{{Related articles start}}
 +
{{Related|Security#Password hashes}}
 +
{{Related articles end}}
  
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''.
+
The Secure Hash Algorithms (SHA) are a set of [[Wikipedia:Cryptographic_hash_function|hash functions]] often used to encrypt passwords. By default Arch uses  SHA-512 for passwords, but some systems may still be using the older [[Wikipedia:MD5|MD5]] algorithm. This article describes how to increase password security.
 +
 
 +
== Benefits of SHA-2 over MD5 ==
 +
 
 +
{{Style|This section should perhaps be pruned and merged with article summary.}}
  
==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 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.
 
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.
  
==Increasing Security==
+
== Increasing security ==
{{note|You must have root privileges to edit this file.}}
+
 
 +
{{Style|The notes and structure of this section lack focus and clarity.}}
 +
 
 +
{{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]).}}
 +
 
 +
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''.
 +
 
 +
{{Note|You must have root privileges to edit this file.}}
 +
 
 
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}}.
 
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}}.
  
 
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:
 
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:
 +
 
  password required pam_unix.so sha512 shadow nullok '''rounds=65536'''
 
  password required pam_unix.so sha512 shadow nullok '''rounds=65536'''
  
 
{{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].}}
  
==Re-Hash the Passwords==
+
== 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.
 
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,
+
As root issue the following command,
  # passwd <username>
+
 
where {{ic|<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.
+
  # passwd ''username''
 +
 
 +
where {{ic|''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 {{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==
+
== Known problems ==
===fgetty===
+
 
 +
=== 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.
 
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.
+
A patched version of ''fgetty'' is in the [[AUR]] named {{AUR|fgetty-pam}}{{Broken package link|{{aur-mirror|fgetty-pam}}}} which adds SHA-512 support.

Latest revision as of 15:37, 28 November 2015

Related articles

The Secure Hash Algorithms (SHA) are a set of hash functions often used to encrypt passwords. By default Arch uses SHA-512 for passwords, but some systems may still be using the older MD5 algorithm. This article describes how to increase password security.

Benefits of SHA-2 over MD5

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: This section should perhaps be pruned and merged with article summary. (Discuss in Talk:SHA password hashes#)

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

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: The notes and structure of this section lack focus and clarity. (Discuss in Talk:SHA password hashes#)
Note: With shadow 4.1.4.3-3 sha512 is the default for new passwords (see bug 13591).

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.

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 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[broken link: archived in aur-mirror] which adds SHA-512 support.