svn: /phpdoc/en/trunk/reference/password/functions/ password-hash.xml

From: Date: Mon, 14 Dec 2015 19:27:01 +0000
Subject: svn: /phpdoc/en/trunk/reference/password/functions/ password-hash.xml
Groups: php.doc.cvs 
Request: Send a blank email to doc-cvs+get-13883@lists.php.net to get a copy of this message
aharvey Mon, 14 Dec 2015 19:27:01 +0000 Revision: http://svn.php.net/viewvc?view=revision&revision=338252 Log: Note that salt is deprecated all over the password_hash() page. Also change the version examples, since some of them have already happened. Now we can forget about this until 2021! Changed paths: U phpdoc/en/trunk/reference/password/functions/password-hash.xml Modified: phpdoc/en/trunk/reference/password/functions/password-hash.xml =================================================================== --- phpdoc/en/trunk/reference/password/functions/password-hash.xml 2015-12-14 14:01:31 UTC (rev 338251) +++ phpdoc/en/trunk/reference/password/functions/password-hash.xml 2015-12-14 19:27:01 UTC (rev 338252) @@ -254,9 +254,15 @@ &reftitle.notes; <caution> <para> - It is strongly recommended that you do not generate your own salt for this function. - It will create a secure salt automatically for you if you do not specify one. + It is strongly recommended that you do not generate your own salt for this + function. It will create a secure salt automatically for you if you do + not specify one. </para> + <para> + As noted above, providing the <literal>salt</literal> option in PHP 7.0 + will generate a deprecation warning. Support for providing a salt manually + may be removed in a future PHP release. + </para> </caution> <note> <para> @@ -273,16 +279,19 @@ <para> <itemizedlist> <listitem> - <simpara>Any new algorithm must be in core for at least 1 full release of PHP prior to becoming - default. So if, for example, a new algorithm is added in 5.5.5, it would not be eligible for - default until 5.7 (since 5.6 would be the first full release). But if a different algorithm was - added in 5.6.0, it would also be eligible for default at 5.7.0. + <simpara> + Any new algorithm must be in core for at least 1 full release of PHP + prior to becoming default. So if, for example, a new algorithm is added + in 7.5.5, it would not be eligible for default until 7.7 (since 7.6 + would be the first full release). But if a different algorithm was added + in 7.6.0, it would also be eligible for default at 7.7.0. </simpara> </listitem> <listitem> <simpara> - The default should only change on a full release (5.6.0, 6.0.0, etc) and not on a revision release. - The only exception to this is in an emergency when a critical security flaw is found in the current + The default should only change in a full release (7.3.0, 8.0.0, etc) + and not in a revision release. The only exception to this is in an + emergency when a critical security flaw is found in the current default. </simpara> </listitem>

« previous php.doc.cvs (#13883) next »