2010-03-28 22:10:10 +00:00
<?xml version="1.0" encoding="utf-8"?>
2009-07-11 09:08:43 +00:00
<!-- $Revision$ -->
2010-02-15 12:13:37 +00:00
<refentry xmlns:xlink= "http://www.w3.org/1999/xlink" xmlns= "http://docbook.org/ns/docbook" xml:id= "function.crypt" >
2007-06-11 00:50:00 +00:00
<refnamediv >
<refname > crypt</refname>
2010-02-21 03:56:09 +00:00
<refpurpose > One-way string hashing</refpurpose>
2007-06-11 00:50:00 +00:00
</refnamediv>
2010-02-27 09:01:19 +00:00
2019-01-09 18:00:01 +00:00
<refsynopsisdiv >
¬e.not-bin-safe;
</refsynopsisdiv>
2007-06-11 00:50:48 +00:00
<refsect1 role= "description" >
&reftitle.description;
2007-06-11 00:50:00 +00:00
<methodsynopsis >
<type > string</type> <methodname > crypt</methodname>
2020-12-03 08:54:27 +00:00
<methodparam > <type > string</type> <parameter > string</parameter> </methodparam>
<methodparam > <type > string</type> <parameter > salt</parameter> </methodparam>
2007-06-11 00:50:00 +00:00
</methodsynopsis>
<para >
2010-02-21 03:56:09 +00:00
<function > crypt</function> will return a hashed string using the
standard Unix <abbrev > DES</abbrev> -based algorithm or
2021-01-02 00:15:51 +00:00
alternative algorithms.
2007-06-11 00:50:00 +00:00
</para>
2013-10-30 22:13:59 +00:00
<para >
2021-01-02 00:15:51 +00:00
The <parameter > salt</parameter> parameter is optional. However, <function > crypt</function> creates a weak hash without the <parameter > salt</parameter> , and raises an <constant > E_NOTICE</constant> error without it. Make sure to specify a strong enough salt for better security.
2013-10-30 22:13:59 +00:00
</para>
<para >
2014-12-29 12:49:12 +00:00
<function > password_hash</function> uses a strong hash, generates a strong salt, and applies proper rounds automatically. <function > password_hash</function> is a simple <function > crypt</function> wrapper and compatible with existing password hashes. Use of <function > password_hash</function> is encouraged.
2013-10-30 22:13:59 +00:00
</para>
2007-06-11 00:50:48 +00:00
<para >
2021-01-02 00:15:51 +00:00
The hash type is triggered by the salt argument.
If no salt is provided, PHP will
2010-02-21 03:56:09 +00:00
auto-generate either a standard two character (DES) salt, or a twelve
character (MD5), depending on the availability of MD5 crypt(). PHP sets a
constant named <constant > CRYPT_SALT_LENGTH</constant> which indicates the
longest valid salt allowed by the available hashes.
2007-06-11 00:50:48 +00:00
</para>
<para >
2010-02-21 03:56:09 +00:00
The standard DES-based <function > crypt</function> returns the
2007-06-11 00:50:00 +00:00
salt as the first two characters of the output. It also only uses the
2020-12-03 08:54:27 +00:00
first eight characters of <parameter > string</parameter> , so longer strings
2007-06-11 00:50:00 +00:00
that start with the same eight characters will generate the same result
(when the same salt is used).
2007-06-11 14:39:35 +00:00
</para>
2007-06-11 00:50:00 +00:00
<simpara >
2021-01-02 00:15:51 +00:00
The following hash types are supported:
2007-06-11 00:50:00 +00:00
</simpara>
<itemizedlist >
<listitem >
2002-04-15 00:12:54 +00:00
<simpara >
2010-02-21 03:56:09 +00:00
<constant > CRYPT_STD_DES</constant> - Standard DES-based hash with a two character salt
2010-03-30 11:42:08 +00:00
from the alphabet "./0-9A-Za-z". Using invalid characters in the salt will cause
crypt() to fail.
2002-04-15 00:12:54 +00:00
</simpara>
2007-06-11 00:50:00 +00:00
</listitem>
<listitem >
2002-04-15 00:12:54 +00:00
<simpara >
2010-02-21 03:56:09 +00:00
<constant > CRYPT_EXT_DES</constant> - Extended DES-based hash. The "salt" is a
2010-02-21 03:32:45 +00:00
9-character string consisting of an underscore followed by 4 bytes of iteration count and
4 bytes of salt. These are encoded as printable characters, 6 bits per character, least
2010-03-30 11:42:08 +00:00
significant character first. The values 0 to 63 are encoded as "./0-9A-Za-z". Using invalid
characters in the salt will cause crypt() to fail.
2002-04-15 00:12:54 +00:00
</simpara>
2007-06-11 00:50:00 +00:00
</listitem>
<listitem >
2002-04-15 00:12:54 +00:00
<simpara >
2010-02-21 03:56:09 +00:00
<constant > CRYPT_MD5</constant> - MD5 hashing with a twelve character salt starting with
2007-06-11 00:50:00 +00:00
$1$
2002-04-15 00:12:54 +00:00
</simpara>
2007-06-11 00:50:00 +00:00
</listitem>
<listitem >
2002-04-15 00:12:54 +00:00
<simpara >
2012-07-20 08:39:55 +00:00
<constant > CRYPT_BLOWFISH</constant> - Blowfish hashing with a salt as
follows: "$2a$", "$2x$" or "$2y$", a two digit cost parameter, "$", and
2013-01-12 04:04:32 +00:00
22 characters from the alphabet "./0-9A-Za-z". Using characters outside of
2012-07-20 08:39:55 +00:00
this range in the salt will cause crypt() to return a zero-length string.
The two digit cost parameter is the base-2 logarithm of the iteration
2021-01-02 00:15:51 +00:00
count for the underlying Blowfish-based hashing algorithm and must be
2012-07-20 08:39:55 +00:00
in range 04-31, values outside this range will cause crypt() to fail.
2021-01-02 00:15:51 +00:00
"$2x$" hashes are potentially weak; "$2a$" hashes are compatible and
mitigate this weakness. For new hashes, "$2y$" should be used.
Please refer to
2012-07-20 08:39:55 +00:00
<link xlink:href= "&url.crypt.blowfish;" > this document</link> for full
2021-01-02 00:15:51 +00:00
details of the related security fix.
2010-02-15 12:13:37 +00:00
</simpara>
</listitem>
<listitem >
<simpara >
2010-02-21 03:56:09 +00:00
<constant > CRYPT_SHA256</constant> - SHA-256 hash with a sixteen character salt
2010-02-15 12:13:37 +00:00
prefixed with $5$. If the salt string starts with 'rounds=< N> $', the numeric value of N
is used to indicate how many times the hashing loop should be executed, much like the cost
2010-02-21 03:56:09 +00:00
parameter on Blowfish. The default number of rounds is 5000, there is a minimum of
2010-02-15 12:13:37 +00:00
1000 and a maximum of 999,999,999. Any selection of N outside this range will be truncated to
the nearest limit.
</simpara>
</listitem>
<listitem >
<simpara >
2010-02-21 03:56:09 +00:00
<constant > CRYPT_SHA512</constant> - SHA-512 hash with a sixteen character salt
2010-02-15 12:13:37 +00:00
prefixed with $6$. If the salt string starts with 'rounds=< N> $', the numeric value of N
is used to indicate how many times the hashing loop should be executed, much like the cost
2010-02-21 03:56:09 +00:00
parameter on Blowfish. The default number of rounds is 5000, there is a minimum of
2010-02-15 12:13:37 +00:00
1000 and a maximum of 999,999,999. Any selection of N outside this range will be truncated to
the nearest limit.
2002-04-15 00:12:54 +00:00
</simpara>
2007-06-11 00:50:00 +00:00
</listitem>
</itemizedlist>
2007-06-11 00:50:48 +00:00
</refsect1>
2010-02-27 09:01:19 +00:00
2007-06-11 00:50:48 +00:00
<refsect1 role= "parameters" >
&reftitle.parameters;
<para >
<variablelist >
<varlistentry >
2020-12-03 08:54:27 +00:00
<term > <parameter > string</parameter> </term>
2007-06-11 00:50:48 +00:00
<listitem >
<para >
2010-02-21 03:56:09 +00:00
The string to be hashed.
2007-06-11 00:50:48 +00:00
</para>
2014-01-28 13:10:21 +00:00
<caution >
<para >
Using the <constant > CRYPT_BLOWFISH</constant> algorithm, will result
2020-12-03 08:54:27 +00:00
in the <parameter > string</parameter> parameter being truncated to a
2014-06-27 15:00:47 +00:00
maximum length of 72 characters.
2014-01-28 13:10:21 +00:00
</para>
</caution>
2007-06-11 00:50:48 +00:00
</listitem>
</varlistentry>
<varlistentry >
<term > <parameter > salt</parameter> </term>
<listitem >
<para >
2010-06-10 02:59:05 +00:00
An optional salt string to base the hashing on. If not provided, the
behaviour is defined by the algorithm implementation and can lead to
unexpected results.
2007-06-11 00:50:48 +00:00
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect1>
2010-02-27 09:01:19 +00:00
2007-06-11 00:50:48 +00:00
<refsect1 role= "returnvalues" >
&reftitle.returnvalues;
<para >
2010-02-23 22:08:17 +00:00
Returns the hashed string or a string that is shorter than 13 characters
and is guaranteed to differ from the salt on failure.
2007-06-11 00:50:48 +00:00
</para>
2014-08-28 03:45:57 +00:00
<warning >
<simpara >
When validating passwords, a string comparison function that isn't
vulnerable to timing attacks should be used to compare the output of
2021-01-02 00:15:51 +00:00
<function > crypt</function> to the previously known hash. PHP
2014-08-28 03:45:57 +00:00
provides <function > hash_equals</function> for this purpose.
</simpara>
</warning>
2007-06-11 00:50:48 +00:00
</refsect1>
2010-02-27 09:01:19 +00:00
2020-12-03 08:54:27 +00:00
<refsect1 role= "changelog" >
&reftitle.changelog;
<informaltable >
<tgroup cols= "2" >
<thead >
<row >
<entry > &Version; </entry>
<entry > &Description; </entry>
</row>
</thead>
<tbody >
<row >
<entry > 8.0.0</entry>
<entry >
The <parameter > salt</parameter> is no longer optional.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</refsect1>
2007-06-11 00:50:48 +00:00
<refsect1 role= "examples" >
&reftitle.examples;
<para >
<example >
<title > <function > crypt</function> examples</title>
<programlisting role= "php" >
2002-04-15 00:12:54 +00:00
< ![CDATA[
< ?php
2021-01-02 00:15:51 +00:00
// let the salt be automatically generated; not recommended
$hashed_password = crypt('mypassword');
2002-04-15 00:12:54 +00:00
2004-07-05 14:46:20 +00:00
/* You should pass the entire results of crypt() as the salt for comparing a
password, to avoid problems when different hashing algorithms are used. (As
it says above, standard DES-based password hashing uses a 2-character salt,
but MD5-based hashing uses 12.) */
2015-03-02 18:04:08 +00:00
if (hash_equals($hashed_password, crypt($user_input, $hashed_password))) {
2002-04-15 00:12:54 +00:00
echo "Password verified!";
}
?>
2004-07-05 14:46:20 +00:00
]]>
2007-06-11 00:50:48 +00:00
</programlisting>
</example>
2008-12-13 02:06:34 +00:00
</para>
<para >
2007-06-11 00:50:48 +00:00
<example >
<title > Using <function > crypt</function> with htpasswd</title>
<programlisting role= "php" >
2004-07-05 14:46:20 +00:00
< ![CDATA[
< ?php
// Set the password
$password = 'mypassword';
2021-01-02 00:15:51 +00:00
// Get the hash, letting the salt be automatically generated; not recommended
2004-08-05 05:37:20 +00:00
$hash = crypt($password);
2004-07-05 14:46:20 +00:00
?>
2002-04-15 00:12:54 +00:00
]]>
2007-06-11 00:50:48 +00:00
</programlisting>
</example>
2008-12-13 02:06:34 +00:00
</para>
<para >
2007-06-11 00:50:48 +00:00
<example >
2010-02-21 03:56:09 +00:00
<title > Using <function > crypt</function> with different hash types</title>
2007-06-11 00:50:48 +00:00
<programlisting role= "php" >
2004-08-04 16:43:12 +00:00
< ![CDATA[
< ?php
2012-08-01 01:48:12 +00:00
/* These salts are examples only, and should not be used verbatim in your code.
You should generate a distinct, correctly-formatted salt for each password.
*/
2021-01-02 00:15:51 +00:00
echo 'Standard DES: ',
crypt('rasmuslerdorf', 'rl'),
"\n";
echo 'Extended DES: ',
crypt('rasmuslerdorf', '_J9..rasm'),
"\n";
echo 'MD5: ',
crypt('rasmuslerdorf', '$1$rasmusle$'),
"\n";
echo 'Blowfish: ',
crypt('rasmuslerdorf', '$2a$07$usesomesillystringforsalt$'),
"\n";
echo 'SHA-256: ',
crypt('rasmuslerdorf', '$5$rounds=5000$usesomesillystringforsalt$'),
"\n";
echo 'SHA-512: ',
crypt('rasmuslerdorf', '$6$rounds=5000$usesomesillystringforsalt$'),
"\n";
2004-08-04 16:43:12 +00:00
?>
]]>
2007-06-11 00:50:48 +00:00
</programlisting>
2010-02-27 09:01:19 +00:00
&example.outputs.similar;
2007-06-11 00:50:48 +00:00
<screen >
2004-08-04 16:43:12 +00:00
< ![CDATA[
Standard DES: rl.3StKT.4T8M
Extended DES: _J9..rasmBYk8r9AiWNc
MD5: $1$rasmusle$rISCgZzpwk3UhDidwXvin0
2021-01-02 00:15:51 +00:00
Blowfish: $2y$07$usesomesillystringfore2uDLvp1Ii2e./U9C8sBjqp8I90dH6hi
2010-02-15 12:13:37 +00:00
SHA-256: $5$rounds=5000$usesomesillystri$KqJWpanXZHKq2BOB43TSaYhEWsQ1Lr5QNyPCDH/Tp.6
SHA-512: $6$rounds=5000$usesomesillystri$D4IrlXatmP7rx3P3InaxBeoomnAihCKRVQP22JZ6EY47Wc6BkroIuUUBOov1i.S5KPgErtP/EN5mcO.ChWQW21
2004-08-04 16:43:12 +00:00
]]>
2007-06-11 00:50:48 +00:00
</screen>
</example>
</para>
2007-06-11 00:50:00 +00:00
</refsect1>
2010-02-27 09:01:19 +00:00
2007-06-11 00:50:48 +00:00
<refsect1 role= "notes" >
&reftitle.notes;
<note >
<simpara >
There is no decrypt function, since <function > crypt</function> uses a
one-way algorithm.
</simpara>
</note>
</refsect1>
2010-02-27 09:01:19 +00:00
2007-06-11 00:50:48 +00:00
<refsect1 role= "seealso" >
&reftitle.seealso;
<para >
<simplelist >
2014-08-28 03:45:57 +00:00
<member > <function > hash_equals</function> </member>
2013-10-30 22:13:59 +00:00
<member > <function > password_hash</function> </member>
2007-06-11 00:50:48 +00:00
<member > <function > md5</function> </member>
<member > The Unix man page for your crypt function for more information</member>
</simplelist>
</para>
</refsect1>
2010-02-27 09:01:19 +00:00
2007-06-11 00:50:00 +00:00
</refentry>
2002-04-15 00:12:54 +00:00
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
2009-09-25 07:04:39 +00:00
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
2002-04-15 00:12:54 +00:00
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->